Posts Tagged ‘Success’

Success – the Enemy of New Work

Success is the enemy of new work. Past success blocks new work out of fear it will jeopardize future success, and future success blocks new work out of fear future success will actually come to be.

Either way you look at it, success gets in the way of doing new work.

Success itself has no power to block new work.  To generate its power, past success creates the fear of loss in the people doing today’s work. And their fear causes them to block new work.  When we did A we got success, and now you are trying to do B.  B is not A, and may not bring success. I will resist B out of fear of losing the goodness of past success.

As a blocking agent, future success is more ethereal and more powerful because it prevents new work from starting. Future success causes our minds to project the goodness and glory the new work could bring and because our small sense of self doesn’t think we’re worthy, we never start. Where past success creates an enemy in the status quo, future success creates an enemy within ourselves.

But if we replace fear with learning, the game changes.

I’m not trying to displace our past success, I’m trying to learn if we can use it as springboard and back flip into the deep end of our future success. If it works, our learning will refine today’s success and inform tomorrow’s. If it doesn’t work, we’ll learn what doesn’t work and try something else. But not to worry, we’ll make small bets and create big learning. That way when we jump in the puddle, the splash will be small. And if the water’s cold, we’ll stop. But if it’s warm, we’ll jump into a bigger puddle. And maybe we’ll jump together. What do you think? Will you help me learn?

Yes, it’s scary to think about running this small experiment. Not because it won’t work, but because it might. If we learn this could work it would be a game-changer for the company and I’m afraid I’m not worthy of the work. Can you help me navigate this emotional roller coaster? Can you help me learn if this will work?  Can you review the results privately and help me learn what’s going on?  If we don’t learn how to do it, our competitors will. Can you help me start?

Success blocks, but it also pays the bills. And, hopefully it’s always part of the equation. But there are things we can do to take the edge of its blocking power. Acknowledge that new work is scary and focus on learning.  Learning isn’t threatening, and it moves things forward. Show results and ask for comments from people who created past success. Over time, they’ll become important advocates. And acknowledge to yourself that new work creates internal fear, and acknowledge the best way to push through fear is to learn.

Be afraid, make small bets and learn big.

Image credit – Andy Morffew

With innovation you’ve got to feel worthy of the work.

When doing work that’s new, sometimes it seems the whole world is working against you. And, most of the time, it is.  The outside world is impossible to control, so the only way to deal with external resistance is to pretend you don’t hear it. Shut your ears, put your head down and pull with all your might. Define your dream and live it. And don’t look back.  But what about internal resistance?

Where external resistance cannot be controlled and must be ignored, internal resistance, resistance created by you, can be actively managed.  The best way to deal with internal resistance is to prevent its manufacture, but very few can do that. The second best way is to acknowledge resistance is self-made and acknowledge it will always be part of the innovation equation.  Then, understand the traps that cause us to create self-inflicted resistance and learn how to work through them.

The first trap prevents starting.  At the initial stage of a project, two unstated questions power the resistance – What if it doesn’t work? and What if it does work?  If it doesn’t work, the fear is you’ll be judged as incompetent or crazy. The only thing to battle this fear is self-worth. If you feel worthy of the work, you’ll push through the resistance and start.  If it does work, the fear is you won’t know how to navigate success. Again, if you think you’re worthy of the work (the work that comes with success), you and your self-esteem will power through the resistance and start.

Underpinning both questions is a fundamental of new work that is misunderstood – new work is different than standard work.  Where standard work follows a well-worn walking path, new work slashes through an uncharted jungle where there are no maps and no GPS. With standard work, all the questions have been answered, the scope is well established and the sequence of events and timeline are dialed in.   With standard work, everything is known up front. With new work, it’s the opposite. Never mind the answers, the questions are unknown. The scope is uncertain and the sequence of events is yet to be defined. And the timeline cannot be estimated.

But with so much standard work and so little new work, companies expect people to that do the highly creative work to have all the answers up front. And to break through the self-generated resistance, people doing new work must let go of self-imposed expectations that they must have all the answers before starting.  With innovation, the only thing that can be known is how to figure out what’s next. Here’s a generic project plan for new work – do the first thing and then, based on the results, figure out what to do next, and repeat.

To break through the trap that prevents starting, don’t hold yourself accountable to know everything at the start. Instead, be accountable for figuring out what’s next.

The second trap prevents progress. And, like the first trap, resistance-based paralysis sets in because we expect ourselves to have an etched-in-stone project plan and expect we’ll have all the answers up front.  And again, there’s no way to have the right answers when the first bit of work must be done to determine the right questions. If you think you’re worthy of the work, you’ll be able to push through the resistance with the figure out what’s next approach.

When in the middle of an innovation project, hold yourself accountable to figuring out what to do next. Nothing more, nothing less. When the standard work police demand a sequence of events and a timeline, don’t buckle. Tell them you will finish the current task then define the next one and you won’t stop until you’re done.  And if they persist, tell them to create their own project plan and do the innovation work themselves.

With innovation, it depends. With innovation, hold onto your self-worth. With innovation, figure out what’s next.

Image credit — Jonathan Kos-Read


Where there’s fun there is no fear.

spinning-kyraFor those who lead projects and people, failure is always lurking in the background.  And gone unchecked, it can hobble. Despite best efforts to put a shine on it, there’s still a strong negative element to failure.  No two ways about it, failure is mapped with inadequacy and error.  Failure is seen as the natural consequence of making a big mistake.  And there’s a finality to failure.  Sometimes it’s the end of a project and sometimes it’s the end of a career.  Failure severely limits personal growth and new behavior.  But at least failure is visible to the naked eye.  There’s no denying a good train wreck.

A fumble is not failure.  When something gets dropped or when a task doesn’t get done, that’s a fumble.  A fumble is not catastrophic and sometimes not even noteworthy.  A fumble is mapped with  a careless mistake that normally doesn’t happen.  No real cause.  It just happens. But it can be a leading indicator of bigger and badder things to come, and if you’re not looking closely, the fumble can go unnoticed. And the causes and conditions behind the fumble are usually unclear or unknown.  Where failure is dangerous because everyone knows when it happens, fumbles are dangerous because they can go unnoticed.

Floundering is not fumbling. With floundering, nothing really happens.  No real setbacks, no real progress, no real energy. A project that flounders is a project that never reaches the finish line and never makes it to the cemetery.  To recognize floundering takes a lot of experience and good judgment because it doesn’t look like much. But that’s the point – not much is happening.  No wind in the sails and no storm on the horizon.  And to call it by name takes courage because there are no signs of danger.  Yet it’s dangerous for that very reason. Floundering can consume more resources than failure.

Fear is the fundamental behind failing, fumbling and floundering. But unlike failure, no one talks about fear. Talking about fear is too scary. And like fumbling and floundering, fear is invisible, especially if you’re not looking.  Like diabetes, fear is a silent killer. And where diabetes touches many, fear gets us all. Fear is invisible, powerful and prolific.  It’s a tall order to battle the invisible.

But where there’s fun there can be no fear. More precisely, there can be no negative consequence of fear. When there’s fun, everyone races around like their hair is on fire.  Not on fire in the burn unit way, but on fire in the energy to burn way. When there’s fun people help each other for no reason. They share, they communicate and they take risks.  When there’s fun no one asks for permission and the work gets done.  When there’s fun everyone goes home on time and their spouses are happy.  Fun is easy to see, but it’s not often seen because it’s rare.

If there’s one thing that can go toe-to-toe with fear, it’s fun. It’s that powerful. Fun is so powerful it can turn failure into learning.  But if it’s so powerful, why don’t we teach people to have fun? Why don’t we create the causes and conditions so fun erupts?

I don’t know why we don’t promote fun.  But, I do know fun is productive and fun is good for business.  But more important than that, fun is a lot of fun.

Image credit – JoshShculz

The Cycle of Success

coccoon-now-transparentThere’s a huge amount of energy required to help an organization do new work.

At every turn the antibodies of the organization reject new ideas.  And it’s no surprise.  The organization was created to do more of what it did last time.  Once there’s success the organization forms structures to make sure it happens again.  Resources migrate to the successful work and walls form around them to prevent doing yet-to-be-successful work. This all makes sense while the top line is growing faster than the artificially set growth goal.  More resources applied to the successful leads to a steeper growth rate.  Plenty of work and plenty of profit.  No need for new ideas.  Everyone’s happy.

When growth rate of the successful company slows below arbitrary goal, the organization is slow to recognize it and slower to acknowledge it and even slower to assign true root cause.  Instead, the organization doubles down on what it knows.  More resources are applied, efficiency improvements are put in place, and clearer metrics are put in place to improve accountability.  Everyone works harder and works more hours and the growth rate increases a bit.  Success.  Except the success was too costly.  Though total success increased (growth), success per dollar actually decreased.  Still no need for new ideas.  Everyone’s happy, but more tired.

And then growth turns to contraction. With no more resources move to the successful work, accountability measures increase to unreasonable levels and people work beyond their level of effectiveness. But this time growth doesn’t come.  And because people are too focused on doing more of what used to work, new ideas are rejected.  When a new idea is proposed, it goes something like this “We don’t need new ideas, we need growth.  Now, get out of my way.  I’m too busy for your heretical ideas.”  There’s no growth and no tolerance for new ideas.  No one is happy.

And then a new idea that had been flying under the radar generates a little growth.  Not a lot, but enough to get noticed.  And when the old antibodies recognize the new ideas and try to reject it, they cannot.  It’s too late.  The new idea has developed a protective layer of growth and has become a resistant strain.  One new idea has been tolerated. Most are unhappy because there’s only one small pocket of growth and a few are happy because there’s one small pocket of growth.

It’s difficult to get the first new idea to become successful, but it’s worth the effort.  Successful new ideas help each other and multiply.  The first one breaks trail for the second one and the second one bolsters the third.  And as these new ideas become more successful something special happens.  Where they were resistant to the antibodies they become stronger than the antibodies and eat them.

Growth starts to grow and success builds on success.  And the cycle begins again.

Image credit – johnmccombs

Rule 1: Don’t start a project until you finish one.

done!One of the biggest mistakes I know is to get too little done by trying to do too much.

In high school we got too comfortable with partial credit. Start the problem the right way, make a few little mistakes and don’t actually finish the problem – 50% credit.  With product development, and other real life projects, there’s no partial credit.  A project that’s 90% done is worth nothing.  All the expense with none of the benefit.  Don’t launch, don’t sell. No finish, no credit.

But our ill-informed focus on productivity has hobbled us.  Because we think running projects in parallel is highly efficient, we start too many projects.  This glut does nothing more than slow down all the other projects in the pipeline.  It’s like we think queuing theory isn’t real because we don’t understand it.  But to be fair to queuing and our stockholders, queuing theory is real.

Queues are nothing more than a collection of wayward travelers waiting in line for a shared resource.  Wait in line for fast food, you’re part of a queue.  Wait in line for a bank teller (a resource,) you’re queued up.  Wait in line to board a plane, you’re waiting in a queue.  But the name isn’t important.  Line or queue, what matters is how long you wait.

Lines are queues and queues are lines, but the math behind them is funky.  From firsthand experience we know longer queues mean longer wait times. And if the cashier isn’t all that busy (in queuing language – the utilization of the resource is low) the wait time isn’t all that bad and it increases linearly with the number of people (or jobs) in the queue.  When the shared resource (cashier) isn’t highly utilized (not all that busy), add a few more shoppers per hour and wait times increase proportionately. But, and this is a big but, if the resource busy more than 80% of the time, increasing the number of shoppers increases the wait time astronomically (or exponentially.)  When shoppers arrive in front of the cashier just a bit more often, wait times can double or triple or more.

For wait times, the math of queueing theory says one plus one equals two and one plus one plus one equals seven.  Wait times increase linearly right up until they explode.  And when wait times explode, projects screech to a halt.  And because there’s no partial credit, it’s a parking lot of projects without any of the profit.  And what’s the worst thing to do when projects aren’t finishing quickly enough?  Start more projects.  And what do we do when projects aren’t launching quickly enough?  Start more projects.

When there’s no partial credit, instead of efficiency it’s better to focus on effectiveness.  Instead of counting the number of projects running in parallel (efficiency,) count the number of projects that have finished (effectiveness.)  To keep wait times reasonable, fiercely limit the amount of projects in the system.  And there’s a simple way to do that.  Figure out the sweet spot for your system, say, three projects in parallel, and create three project “tickets.” Give one ticket to the three active projects and when the project finishes, the project ticket gets assigned to the next project so it can start.  No project can start without a ticket.  No ticket, no project.

This simple ticket system caps the projects, or work in process (WIP,) so shared resources are utilized below 80% and wait times are low. Projects will sprint through their milestones and finish faster than ever.

By starting fewer projects you’ll finish more.  Stop starting and start finishing.

Image credit – Fred Moore

Always Tight on Time

HourglassThere always far more tasks than there is time.  Same for vacations and laundry.  And that’s why it’s important to learn when-and how-to say no.  No isn’t a cop-out.  No is ownership of the reality we can’t do everything.  The opposite of no isn’t maybe; the opposite of no is yes while knowing full well it won’t get done.  Where the no-in-the-now is skillful, the slow no is unskillful.

When you know the work won’t get done and when you know the trip to the Grand Canyon won’t happen, say no.  Where yes is the instigator of dilution, no is the keystone of effectiveness.

And once it’s yes, Parkinson’s law kicks you in the shins.  It’s not Parkinson’s good idea or Parkinson’s conjecture – it’s Parkinson’s law.  And it’s a law is because the work does, in fact, always fill the time available for its completion.  If the work fills the time available, it makes sense to me to define the time you’ll spend on a task before starting the task.  More important tasks are allocated more time, less important tasks get less and the least important get a no-in-the-now.  To beat Parkinson at his own game, use a timer.

Decide how much time you want to spend on a task.  Then, to improve efficiency, divide by two.  Set a countdown timer (I like Timer) and display it in the upper right corner of your computer screen. (As I write this post, my timer has 1:29 remaining.) As the timer counts down you’ll converge on completeness.

80% right, 100% done is a good mantra.

I guess I’m done now.

Image credit — bruno kvot




Channel your inner sea captain.

never ever give upWhen it’s time for new work, the best and smartest get in a small room to figure out what to do.  The process is pretty simple: define a new destination, and, to know when they journey is over, define what it looks like to live there.  Define the idealized future state and define the work to get there.  Turn on the GPS, enter the destination and follow the instructions of the computerized voice.

But with new work, the GPS analogy is less than helpful.  Because the work is new, there’s no telling exactly where the destination is, or whether it exists at all.  No one has sold a product like the one described in the idealized future state.  At this stage, the product definition is wrong.  So, set your course heading for South America though the destination may turn out to be Europe.  No matter, it’s time to make progress, so get in the car and stomp the accelerator.

But with new work there is no map.  It’s never been done before.  Though unskillful, the first approach is to use the old map for the new territory.  That’s like using map data from 1928 in your GPS.  The computer voice will tell you to take a right, but that cart path no longer exists.  The GPS calls out instructions that don’t match the street signs and highway numbers you see through the windshield.  When the GPS disagrees with what you see with your eyeballs, the map is wrong.  It’s time to toss the GPS and believe the territory.

With new work, it’s not the destination that’s important, the current location is most important.  The old sea captains knew this.  Site the stars, mark the time, and set a course heading.  Sail for all your worth until the starts return and as soon as possible re-locate the ship, set a new heading and repeat.  The course heading depends more on location than destination.  If the ship is east of the West Indies, it’s best to sail west, and if the ship is to the north, it’s best to sail south.  Same destination, different course heading.

When the work is new, through away the old maps and the GPS and channel your inner sea caption. Position yourself with the stars, site the landmarks with your telescope, feel the wind in your face and use your best judgement to set the course heading.  And as soon as you can, repeat.

Image credit – Timo Gufler.

If you don’t know the critical path, you don’t know very much.

ouija queenOnce you have a project to work on, it’s always a challenge to choose the first task.  And once finished with the first task, the next hardest thing is to figure out the next next task.

Two words to live by: Critical Path.

By definition, the next task to work on is the next task on the critical path.  How do you tell if the task is on the critical path?  When you are late by one day on a critical path task, the project, as a whole, will finish a day late.  If you are late by one day and the project won’t be delayed, the task is not on the critical path and you shouldn’t work on it.

Rule 1: If you can’t work the critical path, don’t work on anything.

Working on a non-critical path task is worse than working on nothing.  Working on a non-critical path task is like waiting with perspiration.  It’s worse than activity without progress.  Resources are consumed on unnecessary tasks and the resulting work creates extra constraints on future work, all in the name of leveraging the work you shouldn’t have done in the first place.

How to spot the critical path? If a similar project has been done before, ask the project manager what the critical path was for that project.  Then listen, because that’s the critical path.  If your project is similar to a previous project except with some incremental newness, the newness is on the critical path.

Rule 2: Newness, by definition, is on the critical path.

But as the level of newness increases, it’s more difficult for project managers to tell the critical path from work that should wait.  If you’re the right project manager, even for projects with significant newness, you are able to feel the critical path in your chest.  When you’re the right project manager, you can walk through the cubicles and your body is drawn to the critical path like a divining rod.   When you’re the right project manager and someone in another building is late on their critical path task, you somehow unknowingly end up getting a haircut at the same time and offering them the resources they need to get back on track.  When you’re the right project manager, the universe notifies you when the critical path has gone critical.

Rule 3: The only way to be the right project manager is to run a lot of projects and read a lot.  (I prefer historical fiction and biographies.)

Not all newness is created equal.  If the project won’t launch unless the newness is wrestled to the ground, that’s level 5 newness. Stop everything, clear the decks, and get after it until it succumbs to your diligence.  If the product won’t sell without the newness, that’s level 5 and you should behave accordingly.  If the newness causes the product to cost a bit more than expected, but the project will still sell like nobody’s business, that’s level 2.  Launch it and cost reduce it later.  If no one will notice if the newness doesn’t make it into the product, that’s level 0 newness. (Actually, it’s not newness at all, it’s unneeded complexity.)  Don’t put in the product and don’t bother telling anyone.

Rule 4: The newness you’re afraid of isn’t the newness you should be afraid of.

A good project plan starts with a good understanding of the newness.  Then, the right project work is defined to make sure the newness gets the attention it deserves.  The problem isn’t the newness you know, the problem is the unknown consequence of newness as it ripples through the commercialization engine. New product functionality gets engineering attention until it’s run to ground.  But what if the newness ripples into new materials that can’t be made or new assembly methods that don’t exist?  What if the new materials are banned substances?  What if your multi-million dollar test stations don’t have the capability to accommodate the new functionality?  What if the value proposition is new and your sales team doesn’t know how to sell it?  What if the newness requires a new distribution channel you don’t have? What if your service organization doesn’t have the ability to diagnose a failure of the new newness?

Rule 5: The only way to develop the capability to handle newness is to pair a soon-to-be great project manager with an already great project manager. 

It may sound like an inefficient way to solve the problem, but pairing the two project managers is a lot more efficient than letting a soon-to-be great project manager crash and burn.  After an inexperienced project manager runs a project into the ground, what’s the first thing you do?  You bring in a great project manager to get the project back on track and keep them in the saddle until the product launches.  Why not assume the wheels will fall off unless you put a pro alongside the high potential talent?

Rule 6: When your best project managers tell you they need resources, give them what they ask for.

If you want to deliver new value to new customs there’s no better way than to develop good project managers.  A good project manager instinctively knows the critical path; they know how the work is done; they know to unwind situations that needs to be unwound; they have the personal relationships to get things done when no one else can; because they are trusted, they can get people to bend (and sometimes break) the rules and feel good doing it; and they know what they need to successfully launch the product.

If you don’t know your critical path, you don’t know very much.  And if your project managers don’t know the critical path, you should stop what you’re doing, pull hard on the emergency break with both hands and don’t release it until you know they know.

Image credit – Patrick Emerson

Battling the Dark Arts of Productivity and Accountability

warlockHow did you get to where you are?  Was it a series of well-thought-out decisions or a million small, non-decisions that stacked up while you weren’t paying attention? Is this where you thought you’d end up?  What do you think about where you are?

It takes great discipline to make time to evaluate your life’s trajectory, and with today’s pace it’s almost impossible.  Every day it’s a battle to do more than yesterday.  Nothing is good enough unless it’s 10% better than last time, and once it’s better, it’s no longer good enough.  Efficiency is worked until it reaches 100%, then it’s redefined to start the game again.  No waste is too small to eliminate. In business there’s no counterbalance to the economists’ false promise of never-ending growth, unless you provide it for yourself.

If you make the time, it’s easy to plan your day and your week. But if you don’t make the time, it’s impossible.  And it’s the same for the longer term – if you make the time to think about what you want to achieve, you have a better chance of achieving it – but it’s more difficult to make the time.  Before you can make the time to step back and take look at the landscape, you’ve got to be aware that it’s important to do and you’re not doing it.

Providing yourself the necessary counterbalance is good for you and your family, and it’s even better for business.  When you take a step back and slow your pace from sprint to marathon, you are happier and healthier and your work is better.  When scout the horizon and realize you and your work are aligned, you feel better about the work and, therefore, you feel better about yourself.  You’re a better person, partner and parent.  And your work is better.  When the work fits, everything is better.

Sometimes, people know their work doesn’t fit and purposefully don’t take a step back because it’s too scary to acknowledge there’s a problem.  But burying your head doesn’t fix things.  If you know you’re out of balance, the best thing to do is admit it and start a dialog with yourself and your boss.  It won’t get better immediately, but you’ll feel better immediately.  But most of the time, people don’t make time to take a step back because of the blistering pace of the work.  There’s simply no time to think about the future.  What’s missing is a weapon to battle the black arts of productivity and accountability.

The only thing powerful enough to counterbalance the forces of darkness is the very weapon we use to create the disease of hyper-productivity – the shared calendar (MS Calendar, Google Calendar).  Open up the software, choose your day, choose your time and set up a one hour weekly meeting with yourself.  Attendees: you.  Agenda: take a couple deep breaths, relax and think.  Change your settings so no one can see the meeting title and agenda and choose the color that makes people think the meeting is off-site.  With your time blocked, you now have a reason to say no to other meetings.  “Sorry, I can’t attend. I have a meeting.”

This simple mechanism is all you need.

No more excuses.  Make the time for yourself.  You’re worth it.

image credit :jovian (image modified)

Patents are supposed to improve profitability.

wrong AnswerEveryone likes patents, but few use them as a business tool.

Patents define rights assigned by governments to inventors (really, the companies they work for) where the assignee has the right to exclude others from practicing the concepts described in the patent claims.  And patent rights are limited to the countries that grant patents.  If you want to get patent rights in a country, you submit your request (application) and run their gauntlet.  Patents are a country-by-country business.

Patents are expensive.  Small companies struggle to justify the expense of filing a single patent and big companies struggle to justify the expense of their portfolio.  All companies want to reduce patent costs.

The patent process starts with invention.  Someone must go to the lab and invent something.  The invention is documented by the inventor (invention disclosure) and the invention is scored by a cross-functional team to decide if it’s worthy of filing.  If deemed worthy, a clearance search is done to see if it’s different from all other patents, all products offered for sale, and all the other literature in the public domain (research papers, publications).   Then, then the patent attorneys work their expensive magic to draft a patent application and file it with the government of choice. And when the rejection arrives, the attorneys do some research, address the examiner’s concerns and submit the paperwork.

Once granted, the fun begins.  The company must keep watch on the marketplace to make sure no one sells products that use the patented technology.  It’s a costly, never-ending battle.  If infringement is suspected, the attorneys exchange documents in a cease-and-desist jousting match.  If there’s no resolution, it’s time to go to court where prosecution work turns up the burn rate to eleven.

To reduce costs, companies try to reduce the price they pay to outside law firms that draft their patents.  It’s a race to the bottom where no one wins.  Outside firms get paid less money per patent and the client gets patents that aren’t as good as they could be.  It’s a best practice, but it’s not best.  Treating patent work as a cost center isn’t right.  Patents are a business tool that help companies make money.

Companies are in business to make money and they do that by selling products for more than the cost to make them.  They set clear business objectives for growth and define the market-customers to fuel that growth.  And the growth is powered by the magic engine of innovation.  Innovation creates products/services that are novel, useful and successful and patents protect them.  That’s what patents do best and that’s how companies should use them.

If you don’t have a lot of time and you want to understand a patent, read the claims.  If you have less time, read the independent claims.  Chris Brown, Ph.D.

Patents are all about claims.  The claims define how the invention is different (novel) from what’s tin the public domain (prior art).  And since innovation starts with different, patents fit nicely within the innovation framework. Instead of trying to reduce patent costs, companies should focus on better claims, because better claims means better patents.  Here are some thoughts on what makes for good claims.

Patent claims should capture the novelty of the invention, but sometimes the words are wrong and the claims don’t cover the invention.   And when that happens, the patent issues but it does not protect the invention – all the downside with none of the upside.  The best way to make sure the claims cover the invention is for the inventor to review the claims before the patent is filed.  This makes for a nice closed-loop process.

When a novel technology has the potential to provide useful benefit to a customer, engineers turn those technologies into prototypes and test them in the lab.  Since engineers are minimum energy creatures and make prototypes for only the technologies that matter, if the patent claims cover the prototype, those are good claims.

When the prototype is developed into a product that is sold in the market and the novel technology covered by the claims is what makes the product successful, those are good claims.

If you were to remove the patented technology from the product and your customer would notice it instantly and become incensed, those are the best claims.

Instead of reducing the cost of patents, create processes to make sure the right claims are created.  Instead of cutting corners, embed your patent attorneys in the technology development process to file patents on the most important, most viable technology.  Instead of handing off invention disclosures to an isolated patent team, get them involved in the corporate planning process so they understand the business objectives and operating plans.  Get your patent attorneys out in the field and let them talk to customers.  That way they’ll know how to spot customer value and write good claims around it.

Patents are an important business tool and should be used that way.  Patents should help your company make money.  But patents aren’t the right solution to all problems.  Patent work can be slow, expensive and uncertain.  A more powerful and more certain approach is a strong investment in understanding the market, ritualistic technology development, solid commercialization and a relentless pursuit of speed.  And the icing on the top – a slathering of good patent claims to protect the most important bits.

Image credit – Matthais Weinberger

You probably don’t have an organizational capability gap.

mind the gapThe organizational capability of a company defines its ability to get things done.  If you can’t pull it off, you have an organizational capability problem, or so the traditional thinking goes.

If you don’t have enough people to do the work, and the work is not new, that’s not a capability gap, that’s an organizational capacity gap. Capacity gaps are filled in straightforward ways. 1.) You can hire more people like the ones who do the work today and train them with the people you already have. Or for machines – buy more of the old machines you know and love.  2.) Map the work processes and design out the waste.  Find the piles of paper or long queues and the bottleneck will be right in front.  Figure out how to get more work through bottleneck.  Professional tip – ignore everything but the bottleneck because fixing a non-bottleneck will only make you tired and sweaty and won’t increase throughput.  3.) Move people and machines from the work to create a larger shortfall.  If no one complains, it wasn’t a problem and don’t fix it.  If the complaints skyrocket, use the noise to justify the first or second option.  And don’t let your ego get in the way – bigger teams aren’t better, they’re just bigger.

If your company systematically piles too work on everyone’s plate, you don’t have an organizational capability problem, you have a leadership problem.

If you’re asked to put together a future state organization and define its new capabilities, you don’t have an organizational capability gap.  A capability gap exists only when there’s a business objective that must be satisfied, and a paper exercise to create a future state organization is not a business objective.  Before starting the work, ask for the company’s growth objectives and an explanation of the new work your team will have to do to achieve those objectives.  And ask how much money has been budgeted (and approved) for the future state organization and when you can make the first hire.  This will reduce the urgency of the exercise, and may stop it altogether. And everyone will know there’s no  “organizational capability gap.”

If you’re asked to put together a project plan (with timeline and budget) to create a new technology and present the plan to the CEO next week, you have an organizational capability gap.  If there’s a shortfall in the company’s growth numbers and the VP of business development calls you at home and tells you to put together a plan to create a new market in a new country and present it to her tomorrow, you have an organizational capability gap.  If the VP of sales takes you to a fancy restaurant and asks you to make a napkin sketch of your plan to sell the new product through a new channel, you have an organizational capability gap.

Real organizational capability gaps are rare.  Unless there’s a change, there can be no organizational capability gap.  There can be no gap without a new business deliverable, new technology, new partnership, new product, new market, or new channel.  And without a timeline and an approved budget, I don’t know what you have, but you don’t have organizational capability gap.

Image credit – Jehane

Mike Shipulski Mike Shipulski
Subscribe via Email

Enter your email address:

Delivered by FeedBurner