Blog

''There is one thing stronger than all the armies in the world, and that is an idea whose time has come.'' - Victor Hugo, Histoire d'un crime,' 1852

Archive for the ‘management’ Category


Stay on Track With an Idea Embargo

Posted by:

So you’re about to launch. You’ve done a great job planning and executing this project. And you’re almost ready to unveil your baby to the world.

And this is when people start coming up with new ideas and suggestions. Often it’s a major decision maker such as your boss who thinks a new feature or two is needed. Do you rework everything? How do you consider everyone’s feedback and respectfully decline the advice? That all depends on many factors. In the end, you need to decide what’s the gain. And some of that advice comes from someone you can’t ignore.

What now? Do you rework everything? How do you consider everyone’s feedback and respectfully decline the advice? That all depends on many factors. In the end, you need to decide what’s the gain. If it’s a lousy idea, it’s easy to dismiss. But good ideas at the last minute are very tempting to implement. You have to decide whether they are worth the cost. Make a honest analysis of what the costs and benefits of a change will be. That last-minute idea could make your launch a success.

But even so, the last-minute ideas can derail the most well run project. It’s tough when someone ignores all your planning and work. Where were they when you planned this thing? Now that all the work is done, they want to tell you what you should have done. Implementing a last-minute idea or two could delay launch.

You know what I do? Enforce an idea embargo. While planning a project and creating a time line, I mark the day that no new ideas will be accepted. That’s right. After that day, keep your great ideas to yourself because we have work to do.

I’m not advocating restricting people from contributing to your work. Encourage people to contribute early. The embargo is simply the last step in a series of communications. Seek lots of input. Early.

First, you need to communicate your project schedule. Include dates for each step. That includes idea embargo and project deadline. The embargo cannot be a surprise to anyone. Everyone in your group needs to be aware of the time line.

Get everyone involved in a brainstorming session. Get their ideas now. But this isn’t the final idea harvest. You need to stay open to feedback.

Announce your progress as you complete parts of the project. Show off what you have done and solicit more feedback.

Ask for advice or bounce your ideas off individuals. Include as many perspectives as you can. Give people chances to contribute more ideas.

You need to foster an environment that lets people contribute. They need to feel they can add something beyond their daily tasks. All of this will be a waste if they stay silent because no one listens to them anyway.

At no point are you required to implement every idea suggested. You need to use your best judgment. And you need to communicate why some ideas won’t be included. There will be good ideas that aren’t right or economical for a particular project. The key is that you are using your judgment early in the process.

Even after you declare the embargo, don’t write your project plan in stone. I know what I just wrote. But you need to recognize that markets change, glitches arise and assumptions are wrong. Schedule testing moments when you question how things are going. You may need to adjust ideas and procedures. The key is to recognize change happens and try to plan for it.

Of course none of this will prevent the last-minute idea or change. Scott Belsky of Behance writes that there is a good reason for this:

“Some of the most productive leaders we have interviewed suggest that their greatest realizations often come at very inconvenient times – often when it is almost too late to change. The reason is obvious: brain power is concentrated and more able to grasp the tangible outcome of a project only in the final stages. While the team may want to discourage any last minute changes, you will also want to capitalize and capture these insights.”

Scott writes that you don’t want to discard good ideas simply because they came after a deadline. He advocates patience and feels that will lead to more meaningful engagement. Hey, I’m all for meaningful engagement. I’m just saying you need to start it earlier.

I’m going to stick with my idea embargo. Simply because it puts a lot of emphasis on collecting ideas and engagement very early in the process. That cannot hurt no matter what you do days before launch. By seriously including many views in your planning, you reduce the likelihood someone will have last-minute ideas. Those ideas are collected earlier.

When I figure out how to schedule unforeseen problems, I will let you know.

by Cubicle Curtis

Meetings 101: Always Bring Something to the Table

Posted by:

During family dinners in my household, we’d all bring an item from the kitchen to the table. None was exempt from this ritual. No matter who cooked dinner that night, everyone ended up contributing to the meal because of what they brought to the table. What they brought was incidental–the fact they brought something was what was important.

The same applies in a work environment–especially in meetings. We all have different things we bring to the table. What we bring often depends on the role we have in the organization or the area of expertise we apply every day to our work. None of these are really any different than setting a dinner table – every part of the meal is important.

The Centerpiece Object: CEO

Every table often has a decorative centerpiece; it generally reflects the time of year or a mood that is trying to be set. While the table can be a metaphor for the company as a whole, the centerpiece is the thing that ties it all together. I’d liken it to the CEO or person ensuring the mandate and mission of the office is being met. The centerpiece is the focal point: the one thing we don’t lose sight of. If it’s a good centerpiece, you can’t help but admire it. If it’s not, you tend to toss it aside. Ideally, you need to get a good centerpiece.

The Dishes: Management Team

The plates and bowls are meant to take what’s offered and house them so they can be worked on. As with any project, if you put the wrong people in charge of it you’ll end up with a big mess. Similarly, you’re not going to serve soup on a plate. The right dishware is critical to a good meal and the right management are imperative in order to make sure things are properly handled. Not everyone is going to be right for the same tasks every time out, but if you know when and where to utilize these people you’ll have a far easier time managing things. But before you even begin to dig in, you’ll need…

The Utensils: Project Team

Not everything can be eaten with your hands. Most things can’t. The key to getting through a project is having the right tools at your disposal – and those often are the people working on it, day in and day out. They know how to attack the plan and the management team has made it easier for them to do so. They often bring things in that the management team can’t or doesn’t see. They are looking ahead with a different set of eyes. That’s why you don’t see a plate cut a steak. It’s just not “cut” out for it.

(Sorry about that pun. To be fair, I’ve lasted four months without using one.)

The Main Course: The Agenda

This isn’t a person or a role, this is simply what needs to be dealt with. If you have an under-developed agenda, you’re not going to enjoy your meeting very much. More often than not, you won’t even get anything done if it’s not clear and focused. I can tell you that when it comes to dinner, I’m not going to eat undercooked meat. You know why? Because I could get sick – or worse.

That’s what an “undercooked” agenda can do to your organization.

The Dessert: The End Result

Have you ever tried to bake a soufflé? If you have, you’ll know how challenging it is to keep it from falling flat (even if you haven’t, you’ve likely heard about how this can happen). A meeting is similar in that if you don’t handle it accordingly, the end result will fall flat. When a soufflé works out, it tastes great. But a flat one just comes off unappealing – not even worth eating, really. If you want to have a great ending to your meeting, handle it with care throughout. What that means for your office is dependent on a ton of things (your centerpiece comes to mind), but make sure you adhere to it as closely as possible. Otherwise your meeting will fall flat.

The Aperitif: The Rewards

This is post-meeting stuff, but if you are able to have everyone contribute their best stuff – bring something worthwhile to the table and play to your strengths – there will be cause for celebration. Celebration is crucial to team building, so make sure you do it when it is warranted.

When everyone gets together in the office for a meeting, keep in mind the idea that if everyone is asked to bring something to the table, they will. Those that want to put their best forward, will. Those that are interested in the organization’s growth as well as their own, will.

Those that don’t will be left sitting somewhere else altogether.

Mike Vardy

Mike Vardy is the creator of the personal productivity parody site,Eventualism, and the editor  atWorkAwesome. In addition to contributing to other productivity sites (GTD Times, Productive! Magazine), he also co-hosts the weekly pop culture and tech podcast, DyscultureD. Also known as a comedy writer and performer, Mike plies his trade(s) and lives in Victoria, BC, Canada with his wife, daughter and “baby-on-the-way.”

How to Improve Productivity: 6 Lessons from Great Software

Posted by:

Well-written software applications are fast, powerful and flexible: They are remarkably disciplined, following a rigid set of self-imposed rules. Their meticulous organization allows them to keep track of millions of bits of information, and their multitasking ability is unmatched. As air breathing, flesh-and-blood work processors, we could learn quite a bit from our binary-based brethren.

Make yourself accessible

These days, software applications of all shapes and sizes are spawning peripheral programs to enable use on a smartphone, browser or home computer. It seems that every software publisher is scrambling to create iPhone, Blackberry and Droid apps that allow their users to connect from just about anywhere.

You should make yourself similarly accessible. This doesn’t entail staying in the office 24 hours a day, but it does mean leaving an avenue for contact when you’re away. Have faith that your coworkers will respect your working (and nonworking) hours. You might also want to think twice about shutting your office door for hours at a time; that would make you quite inaccessible.

Recover gracefully from a crash

Even the best computer programs (and the best workers) have a meltdown once in a while. Once an irreversible breakdown or a grave mistake happens, the best thing to do is recover gracefully. For a computer program, this would involve resetting, running diagnostics, and checking settings. For you, it might mean taking a step back from the current catastrophe, salvaging what you can, ensuring it doesn’t happen a second time, and proceeding mindful of the cause. If your software is learning from its mistakes, you should certainly be learning from yours.

Don’t hog resources

Poorly-written programs take up unnecessary amounts of memory and processing power. Selfishly, they assume that there are no other operations running and no better use for those resources.

The same can be said for a worker who needs large budgets, multiple meetings, and a lot of coworker’s time to complete some basic, straightforward projects. They ignore the bigger picture, “tunnel-visioning” on the task at hand and sacrificing efficiency in the process. The successful (and inefficient) completion of a project feels very satisfying to the resource hog. You can’t blame them; it always feels good to finish an enormous, multifaceted project. But, not all projects have to be huge, and some can get unnecessarily bloated with milestones, meetings, approval stages and benchmarks.

Swatting a fly with a sledgehammer can certainly feel satisfying, but it’s not good work. Don’t be a resource hog; instead, be a lean, lightweight, high-performance machine.

Update frequently

A good piece of software is continually updated with new fixes and features to keep customers happy. New software is always coming out, and if it’s conceived carefully, it will target the weaknesses of currently available programs and try to trump them.

Just like the steady stream of software coming from Silicon Valley, there are annual floods of fresh graduates coming out of local colleges and training programs, armed with the latest and greatest capabilities. You may have the edge of experience, but you’ll need some “updates” to stay competitive.

If you’re have a weakness at work due to a missing skill set or an unfamiliarity with a nascent part of your industry, don’t just shrug it off. Find a book, website or podcast that covers the missing information, and integrate it into your workflow. Then, next time your group is looking for “updates” (the kind announced at group meetings), make it known that you’ve addressed a weakness or acquired a new feature within your own programming. Your “users” will certainly appreciate the added value in your “bug fixes” and “new features.”

Be “User-Friendly”

Users will always encounter errors with their software; the handling of such errors is what dictates the program’s “user-friendliness.” Even widely-used programs have indecipherable, frustrating unfriendly errors:

“An unexpected error has occurred while processing this request.”

This kind of nondescript, vague message borders on useless, and makes the software look bad. Friendlier programs will be as helpful as possible in getting you on the right track:

“Oops. It looks like you don’t have room on your computer to install this. You may need to remove some files and/or programs to free up disk space.”

Similarly helpful (and similarly unhelpful) messages can come from humans: If you’re unable to do what’s asked, would you send your users a vague, frustrating response? If you’re truly “user-friendly,” you’ll be as clear as possible in explaining what’s stopping you from running your usual routine. People occasionally accept malformed, incomprehensible errors from computers, but they’ll rarely take the same from a human being.

Work well with others

Compatibility used to be a “nice to have” feature, but now it’s essential for any application. Nearly every software program released today comes with an “Application Programming Interface” (API) that allows it to deliver it’s results to other applications. Programs that lack an effective means to deliver their work to other mediums usually they get phased out by a program that “works well with others.”

To avoid getting phased out yourself, take care to interface well with your fellow carbon-based co-workers. Some have their own organizational systems that involve file names, email subject lines, and carefully-planned schedules. Accommodate their self-made systems; if you deliver the work exactly the way they’d do it themselves, they’ll love the new You 2.0.

Follow through on these 6 lessons, and unlike a computer programn, you may find yourself avoiding obsolesence.

Peter North

Peter is a technology professional living in Washington DC. After studying Spanish and working with various programming languages, he has returned to writing in his native language, English. Peter is always finding enjoyment and satisfaction in his work, often in the strangest places.

Leadership 101

Posted by:  /  Comments: 1

There are two basic types of leaders; those in a leadership position, and those who lead.  One is called a leader because their title or level of seniority (or authority) says so, while one has a calling to be a leader.

It’s important to be able to tell the difference between the two.

The person in the leadership position is there because they were either promoted to the position since they excelled in their previous role (some might refer to this situation as thePeter Principle – promoted to their highest level of incompetence – like this example), or they were promoted to the position out of friendship, favoritism, or an ability (and desire) to “lay down the law” as required.  This person will get your company results, but they often aren’t able to trust that their team can perform without them.  “By the Book,” “My way or the highway,” and “Because I said so” are frequent justifications for their leadership decisions.

On the other hand, a leader is the person that makes you want to follow them.  There is something about them that draws you to them, whether it’s the way they encourage you to do the best you can, the way they train you to do things right, or it’s just the way they demonstrate their respect for being part of the team.  A leader will allow you to grow as a person and as a coworker.   They understand their success comes from your success; when you do well, they do well.

What is a leader?

  • A great leader will get more out of you than the strictest supervisor ever will.  A leader doesn’t manipulate you or try to trick you into doing extra work when they need it.
  • A leader listens before they make a decision.  They will talk with their bosses to find out what needs to be done, and to their team to find out how to do it.
  • A leader understands the job can’t be done without you.  A leader doesn’t see you as a tool they need to use to get the job done.

“The best executive is the one who has sense enough to pick good men to do what he wants done, and self-restraint to keep from meddling with them while they do it.”

- Theodore Roosevelt

Is a leader always in a leadership role?  Nope.  It might be the newest member on the team that does the true leading.  Think back to some of the projects that you were in charge of.  Were you the one leading the team, or were you just the one giving the orders?

“Management is doing things right; leadership is doing the right things.”

- Peter F. Drucker

Even if you see yourself in the first category, there’s still hope.  You can choose to be a leader by working with your team.

Here are five easy steps to help you become a great leader.

1. Tell your team what you need

If you want to make things happen, let your team know what needs to be done.  If you’ve done your job right, they are already experts.  They know how to do their job, all they need is for you to get out of the way.  Tell them what you need, and let them come up with the plan on how to get there.

“Don’t tell people how to do things, tell them what to do and let them surprise you with their results.”

- George S. Patton

2. Give them the tools, time, and training they require

If you prepare your team properly, they’ll be able to handle just about anything in your business.  Well, even if you don’t prepare them, they’ll figure a way to make it happen, but it’s much better for you if you invest the time and energy into a structured training program that helps them develop their skills.

3. Ask your team what they need

Once you’ve told your team what you need, ask them what they need to make it happen.  This can be difficult for some managers, as they think the team is going to make outrageous demands.  If you’re being open and honest with your team, chances are they’ll be open and honest with you about their needs.  I’ll bet you dollars to donuts they won’t ask for as much as you think they would.  This helps create realistic expectations on timelines and budgets, which you can share with your bosses.

4. Encourage your team as they work

Regular communication is key.  Don’t wait until the day of the deadline to check in with them.  Find out as they go along how the project is faring.  This way you can help them overcome barriers if they need it, or praise them if they are on or ahead of schedule.

5. Thank them for being on the team, share the reward with them

Appreciate your people.  If they do a good job, show them that you are grateful.  This doesn’t mean throw  a big party every time you finish a quarter, but it does mean you should genuinely thank them for a successful project.  If your team helps you get your bonus, it makes sense to pass some of it along to them.  If you have a bonus structure, make sure they benefit from it too – 70% of something is much better than 100% of nothing.

“I must follow the people. Am I not their leader?”

- Benjamin Disraeli

Are you a manager or a leader?  If you are a leader, which style do you use to get the job done?

Jason Finnerty

After spending way too long in the corporate world, Jason has switched to full-time freelancing. With any luck you enjoyed this article – and if you need one of your very own, give him a shout! @brandscaping on the twitter, or at brandscaping.ca

Service. Leader’s Role #1 (And #2 & #3 & …)

Posted by:

I have a slide that I invariably use at the top of a presentation:

Organizations exist to serve.

Period.

Leaders exist to serve.

Period.

My abiding penchant for leadership-as-service was supported in Jim Strock‘s superb Serve to Lead. (He will soon be one of our “Cool Friends.”) Here are the bare-bones basics:

Ten Principles of Twenty-first Century Leadership

  1. Everyone can lead because everyone can serve.
  2. The most valuable resource of any enterprise is its people.
  3. We are in transition from a transaction-based world to a relationship-based world.
  4. Leadership is a relationship between empowered, consenting adults.
  5. Leadership is a dynamic relationship.
  6. There is no universal leadership style.
  7. Leadership roles are converging.
  8. A leader’s unique task is to imagine and advance a vision.
  9. Love is the highest level of leadership relationships.
  10. Character is a competitive advantage.

The Four Questions

  1. Who are you serving?
  2. How can you best serve?
  3. Are you making your unique contribution?
  4. Are you getting better every day?

Tom Peters posted this on 06/03, in Service.

Tweets+

Posted by:

Here are a few things I believe are central to success, personal and organizational. In this (selfish) instance, the author is me (some emerged from the gorgeous brevity ofTweets):

EXCELLENCE. Always.
If not EXCELLENCE, what?
If not EXCELLENCE now, when?

EXCELLENCE is not an “aspiration.”
EXCELLENCE is not a “journey.”
EXCELLENCE is the next five minutes.
Organizations exist to serve. Period.
Leaders exist to serve. Period.
Service is a beautiful word.
Service is a beautiful word. Service is character, community, commitment. (And profit.)
Service is a beautiful word. Service is not “Wow.” Service is not “raving fans.” Service is not “an experience.” Service is “just” that—SERVICE.
K = R = P
Kindness = Repeat business = Profit.

Tom Peters posted this on 06/04, in ExcellenceService.