Shipulski On Design

Archive for the ‘Problems’ Category

Additive Manufacturing (AM) is technology/product space with ever-increasing performance and an ever-increasing collection of products. There are many different physical principles used to add material and there are a range of part sizes that can be made ranging from micrometers to tens of meters.  And there is an ever-increasing collection of materials that can be deposited from water soluble plastics to exotic metals to specialty ceramics.

But AM tools and technologies don’t deliver value on their own.  In order to deliver value, companies must deploy AM to solve problems and implement solutions.  But where to start? What to do next? And how do you know when you’ve arrived?

To help with your AM journey, below a maturity model for AM.  There are eight categories, each with descriptions of increasing levels of maturity.  To start, baseline your company in the eight categories and then, once positioned, look to the higher levels of maturity for suggestions on how to move forward.

For a more refined calibration, a formal on-site assessment is available as well as a facilitated process to create and deploy an AM build-out plan.  For information on on-site assessment and AM deployment, send me a note at mike@shipulski.com.

Execution

1. Specify AM machine – There a many types of AM machines. Learn to choose the right machine.
2. Justify AM machine – Define the problem to be solved and the benefit of solving it.
3. Budget for AM machine – Find a budget and create a line item.
4. Pay for machine –  Choose the supplier and payment method – buy it, rent to own, credit card.
5. Install machine – Choose location, provide necessary inputs and connectivity
6. Create shapes/add material – Choose the right CAD system for the job, make the parts.
7. Create support/service systems – Administer the job queue, change the consumables, maintenance.
8. Security – Create a system for CAD files and part files to move securely throughout the organization.
9. Standardize – Once the first machines are installed, converge on a small set of standard machines.
10. Teach/Train – Create training material for running AM machine and creating shapes.

Solution

1. Copy/Replace – Download a shape from the web and make a copy or replace a broken part.
2. Adapt/Improve – Add a new feature or function, change color, improve performance.
3. Create/Learn – Create something new, show your team, show your customers.
4. Sell Products/Services – Sell high volume AM-produced products for a profit. (Stretch goal.)

Volume

1. Make one part – Make one part and be done with it.
2. Make five parts – Make a small number of parts and learn support material is a challenge.
3. Make fifty parts – Make more than a handful of parts. Filament runs out, machines clog and jam.
4. Make parts with a complete manufacturing system – This topic deserves a post all its own.

Complexity

1. Make a single piece – Make one part.
2. Make a multi-part assembly – Make multiple parts and fasten them together.
3. Make a building block assembly – Make blocks that join to form an assembly larger than the build area.
4. Consolidate – Redesign an assembly to consolidate multiple parts into fewer.
5. Simplify – Redesign the consolidated assembly to eliminate features and simplify it.

Material

1. Plastic – Low temperature plastic, multicolor plastics, high performance plastics.
2. Metal – Low melting temperature with low conductivity, higher melting temps, higher conductivity
3. Ceramics – common materials with standard binders, crazy materials with crazy binders.
4. Hybrid – multiple types of plastics in a single part, multiple metals in one part, custom metal alloy.
5. Incompatible materials – Think oil and water.

Scale

1. 50 mm – Not too large and not too small. Fits the build area of medium-sized machine.
2. 500 mm – Larger than the build area of medium-sized machine.
3. 5 m – Requires a large machine or joining multiple parts in a building block way.
4. 0.5 mm – Tiny parts, tiny machines, superior motion control and material control.

Organizational Breadth

1. Individuals – Early adopters operate in isolation.
2. Teams – Teams of early adopters gang together and spread the word.
3. Functions – Functional groups band together to advance their trade.
4. Supply Chain – Suppliers and customers work together to solve joint problems.
5. Business Units – Whole business units spread AM throughout the body of their work.
6. Company – Whole company adopts AM and deploys it broadly.

Strategic Importance

1. Novelty – Early adopters think it’s cool and learn what AM can do.
2. Point Solution – AM solves an important problem.
3. Speed – AM speeds up the work.
4. Profitability – AM improves profitability.
5. Initiative – AM becomes an initiative and benefits are broadly multiplied.
6. Competitive Advantage – AM generates growth and delivers on Vital Business Objectives (VBOs).

Image credit – Cheryl

Everyone knows innovation is difficult, but there’s no best way to make it easier. And everyone knows there’s plenty of opportunities to make innovation more effective, but, again, there’s no best way.  Clearly, there are ways to improve the process, and new tools can help, but the right process improvements depend on the existing process and the specific project.  And it’s the same for tools – the next tool depends on the existing toolbox and the new work required by the project.  With regard to tools and processes, the right next steps are not universal.

But with all companies’ innovation processes, there is a common factor – the innovation process is run by people. Regardless of process maturity or completeness, people run the process.  And this fundamental cuts across language, geography and company culture.  And it cuts across products, services, and business models.  Like it or not, innovation is done by people.

At the highest level, innovation converts ideas into something customers value and delivers the value to them for a profit. At the front end, innovation is about ideas, in the middle, it’s about problems and at the back end, it’s about execution. At the front, people have ideas, define them, evaluate them and decide which ones to advance. In the middle, people define the problems and solve them. And at the back end, people define changes to existing business process and run the processes in a new way.

Tools are a specialized infrastructure that helps people run lower-level processes within the innovation framework. At the front, people have ideas about new tools, or how to use them in a new way, define the ideas, evaluate them, and decide which tools to advance. In the middle, people define problems with the tools and solve them. And at the back end, they run the new tools in new ways.

With innovation processes and tools, people choose the best ideas, people solve problems and people implement solutions.

In order to choose the best ideas, people must communicate the ideas to the decision makers in a clear, rich, nuanced way. The better the idea is communicated, the better the decision. But it’s difficult to communicate an idea, even when the idea is not new. For example, try to describe your business model using just words. And it’s more difficult when the idea is new. Try to describe a new (untested) business model using just your words. For me, words are not a good way to communicate new ideas.

Improved communication improves innovation. To improve communication of ideas, use fewer words. Draw a picture, create a cartoon, make a storyboard, or make a video.  Let the decision maker ask questions of your visuals and respond with another cartoon, a modified storyboard or a new sketch.  Repeat the process until the decision maker stops asking questions.  Because communication is improved, the quality of the decision is improved.

Improved problem solving improves innovation. To improve problem-solving, improve problem definition (the understanding of problem definition.) Create a block diagram of the problem – with elements of the system represented by blocks and labeled with nouns, and with actions and information flow represented by arrows labeled with verbs. Or create a sketch of the customer caught in the act of experiencing the problem.  Define the problem in time (when it happens) so it can be solved before, during or after. And in all cases, limit yourself to one page. Continue to modify the visuals until there’s a common definition of the problem (the words stop.)  When the problem is defined and communicated in this way, the problem solves itself. Problem-solving is seven-eighths problem definition.

Improved execution improves innovation. To improve execution, improve clarity of the definition of success.  And again, minimize the words. Draw a picture that defines success using charts or graphs and data. Create the axes and label them (don’t forget the units of measure). Include data from the baseline product (or process) and define the minimum performance criterion in red.  And add the sample size (number of tests.) Use one page for each definition of success and sequence them in order of importance. Start with the work that has never been done before.  And to go deeper, define the test protocol used to create the data.

For a new business model, the one-page picture could be a process diagram with new blocks for new customers or partners or new arrows for new information flows. There could be time requirements (response time) or throughput requirements (units per month). Or it could be a series of sketches of new deliverables provided by the business model, each with clearly defined criteria to judge success. When communicated clearly to the teams, definitions of success are beacons of light that guide the boats as the tide pulls them through the project or when uncharted rocks suddenly appear to starboard.

Innovation demands communication and communication demands mechanisms. In the domain of uncertainty, words are not the best communicators.  Create visual communication mechanisms that distill and converge on a common understanding.

A picture isn’t worth a thousand words, it gets rid of a thousand.

Image credit – Michael Coghlan

We live in a resource constrained world where there’s always more work than time.  Resources are always tighter than tight and tough choices must be made. The first choice is to figure out what change you want to make in the world. How do you want put a dent in the universe? What injustice do you want to put to rest? Which paradigm do you want to turn on its head?

In business and in life, the question is the same – How do you want to spend your time?

Before you can move in the right direction, you need a direction. At this stage, the best way to allocate your resources is to define the system as it is. What’s going on right now? What are the fundamentals? What are the incentives? Who has power?  Who benefits when things move left and who loses when things go right?  What are the main elements of the system? How do they interact? What information passes between them? You know you’ve arrived when you have a functional model of the system with all the elements, all the interactions and all the information flows.

With an understanding of how things are, how do you want to spend your time? Do you want to validate your functional model? If yes, allocate your resources to test your model. Run small experiments to validate (or invalidate) your worldview.  If you have sufficient confidence in your model, allocate your resources to define how things could be.  How do you want the fundamentals to change? What are the new incentives? Who do you want to have the power? And what are the new system elements, their new interactions and new information flows?

When working in the domain of ‘what could be’ the only thing to worry about is what’s next. What’s after the next step?  Not sure. How many resources will be required to reach the finish line? Don’t know. What do we do after the next step? It depends on how it goes with this step. For those that are used to working within an efficiency framework this phase is a challenge, as there can be no grand plan, no way to predict when more resources will be needed and no way to guarantee resources will work efficiently. For the ‘what could be’ phase, it’s better to use a framework of effectiveness.

In a one-foot-in-front-of-the-other way, the only thing that matters in the ‘what could be’ domain is effectively achieving the next learning objective. It’s not important that the learning is done most efficiently, it matters that the learning is done well and done quickly.  Efficiently learning the wrong thing is not effective. Running experiments efficiently without learning what you need to is not effective. And learning slowly but efficiently is not effective.

Allocate resources to learn what needs to be learned. Allocate resources to learn effectively, not efficiently. Allocate your best people and give them the time they need.  And don’t expect an efficient path. There will be unplanned lefts and rights. There will be U-turns. There will times when there’s lots of thinking and little activity, but at this stage activity isn’t progress, thinking is. It may look like a drunkard’s walk, but that’s how it goes with this work.

When the objective of the work isn’t to solve the problem but to come up with the right question, allocate resources in a way that prioritizes effectiveness over efficiency. When working in the domain of ‘what could be’ allocate resources on the learning objective at hand. Don’t worry too much about the follow-on learning objectives because you may never earn the right to take them on.

In the domain of uncertainty, the best way to allocate the resources is to learn what you need to learn and then figure out what to learn next.

Image credit – John Flannery

The trouble with innovation is it’s risky.  Sure, the upside is nice (increased sales), but the downside (it doesn’t work) is distasteful. Everyone is looking for the magic pill to change the risk-reward ratio of innovation, but there is no pill.  Though there are some things you can do to tip the scale in your favor.

All problems are business problems.  Problem solving is the key to innovation, and all problems are business problems.  And as companies embrace the triple bottom line philosophy, where they strive to make progress in three areas – environmental, social and financial, there’s a clear framework to define business problems.

Start with a business objective.  It’s best to define a business problem in terms of a shortcoming in business results. And the holy grail of business objectives is the growth objective.  No one wants to be the obstacle, but, more importantly, everyone is happy to align their career with closing the gap in the growth objective.  In that way, if solving a problem is directly linked to achieving the growth objective, it will get solved.

Sell more.  The best way to achieve the growth objective is to sell more. Bottom line savings won’t get you there.  You need the sizzle of the top line. When solving a problem is linked to selling more, it will get solved.

Customers are the only people that buy things.  If you want to sell more, you’ve got to sell it to customers. And customers buy novel usefulness.  When solving a problem creates novel usefulness that customers like, the problem will get solved.  However, before trying to solve the problem, verify customers will buy what you’re selling.

No-To-Yes.  Small increases in efficiency and productivity don’t cause customers to radically change their buying habits.  For that your new product or service must do something new. In a No-To-Yes way, the old one couldn’t but the new one can. If solving the problem turns no to yes, it will get solved.

Would they buy it? Before solving, make sure customers will buy the useful novelty. (To know, clearly define the novelty in a hand sketch and ask them what they think.) If they say yes, see the next question.

Would it meet our growth objectives? Before solving, do the math. Does the solution result in incremental sales larger than the growth objective? If yes, see the next question.

Would we commercialize it? Before solving, map out the commercialization work. If there are no resources to commercialize, stop.  If the resources to commercialize would be freed up, solve it.

Defining is solving. Up until now, solving has been premature. And it’s still not time. Create a functional model of the existing product or service using blocks (nouns) and arrows (verbs). Then, to create the problem(s), add/modify/delete functions to enable the novel usefulness customers will buy.  There will be at least one problem – the system cannot perform the new function. Now it’s time to take a deep dive into the physics and bring the new function to life.  There will likely be other problems.  Existing functions may be blocked by the changes needed for the new function. Harmful actions may develop or some functions will be satisfied in an insufficient way.  The key is to understand the physics in the most complete way.  And solve one problem at a time.

Adaptation before creation. Most problems have been solved in another industry. Instead of reinventing the wheel, use TRIZ to find the solutions in other industries and adapt them to your product or service.  This is a powerful lever to reduce innovation risk.

There’s nothing worse than solving the wrong problem.  And you know it’s the wrong problem if the solution doesn’t: solve a business problem, achieve the growth objective, create more sales, provide No-To-Yes functionality customers will buy, and you won’t allocate the resources to commercialize.

And if the problem successfully runs the gauntlet and is worth solving, spend time to define it rigorously.  To understand the bedrock physics, create a functional of the system, add the new functionality and see what breaks.  Then use TRIZ to create a generic solution, search for the solution across other industries and adapt it.

The key to innovation is problem solving. But to reduce the risk, before solving, spend time and energy to make sure it’s the right problem to solve.

It’s far faster to solve the right problem slowly than to solve the wrong one quickly.

Image credit – Kate Ter Haar

There are many definitions for creativity and innovation, but none add meaningfully to how the work is done. Though it’s clear why the work is important – creativity and innovation underpin corporate prosperity and longevity – it’s especially helpful to know how to do it.

At the most basic level, creativity and innovation are about problem solving.  But it’s a special flavor of problem solving.  Creativity and innovation are about problems solving new problems in new ways.  The glamorous part is ‘solving in new ways’ and the important part is solving new problems.

With continuous improvement the same problems are solved over and over. Change this to eliminate waste, tweak that to reduce variation, adjust the same old thing to make it work a little better.  Sure, the problems change a bit, but they’re close cousins to the problems to the same old problems from last decade. With discontinuous improvement (which requires high levels of creativity and innovation) new problems are solved.  But how to tell if the problem is new?

Solving new problems starts with seeing problems differently.

Systems are large and complicated, and problems know how to hide in the nooks and crannies. In a Where’s Waldo way, the nugget of the problem buries itself in complication and misuses all the moving parts as distraction. Problems use complication as a cloaking mechanism so they are not seen as problems, but as symptoms.

Telescope to microscope. To see problems differently, zoom in.  Create a hand sketch of the problem at the microscopic level.  Start at the system level if you want, but zoom in until all you see is the problem.  Three rules: 1. Zoom in until there are only two elements on the page. 2. The two elements must touch. 3. The problem must reside between the two elements.

Noun-verb-noun. Think hammer hits nail and hammer hits thumb.  Hitting the nail is the reason people buy hammers and hitting the thumb is the problem.

A problem between two things. The hand sketch of the problem would show the face of the hammer head in contact with the surface of the thumb, and that’s all.  The problem is at the interface between the face of the hammer head and the surface of the thumb. It’s now clear where the problem must be solved. Not where the hand holds the shaft of the hammer, not at the claw, but where the face of the hammer smashes the thumb.

Before-during-after. The problem can be solved before the hammer smashes the thumb, while the hammer smashes the thumb, or after the thumb is smashed.  Which is the best way to solve it? It depends, that’s why it must be solved at the three times.

Advil and ice. Solving the problem after the fact is like repair or cleanup. The thumb has been smashed and repercussions are handled in the most expedient way.

Put something between. Solving the problem while it happens requires a blocking or protecting action. The hammer still hits the thumb, but the protective element takes the beating so the thumb doesn’t.

Hand in pocket. Solving the problem before it happens requires separation in time and space. Before the hammer can smash the thumb it is moved to a safe place – far away from where the hammer hits the nail.

Nail gun. If there’s no way for the thumb to get near the hammer mechanism, there is no problem.

Cordless drill. If there are no nails, there are no hammers and no problem.

Concrete walls. If there’s no need for wood, there’s no need for nails or a hammer. No hammer, no nails, no problem.

Discerning between symptoms and problems can help solve new problems. Seeing problems at the micro level can result in new solutions. Looking closely at problems to separate them time and space can help see problems differently.

Eliminating the tool responsible for the problem can get rid of the problem of a smashed thumb, but it creates another – how to provide the useful action of the driven nail.  But if you’ve been trying to protect thumbs for the last decade, you now have a chance to design a new way to fasten one piece of wood to another, create new walls that don’t use wood, or design structures that self-assemble.

Image credit – Rodger Evans

When it’s time to innovate, the first task is usually to define the Idealized Future State (IFS).  The IFS is a word picture that captures what it looks like when the innovation work has succeeded beyond our wildest dreams. The IFS, so it goes, is directional so we can march toward the right mountain and inspirational so we can sustain our pace over the roughest territory.

For the IFS to be directional, it must be aimed at something – a destination.  But there’s a problem. In a sea of uncertainty, where the work has never been done before and where there are no existing products, services or customers, there are an infinite number of IFRs/destinations to guide our innovation work.  Open question – When the territory is unknown, how do we choose the right IFS?

For the IFS to be inspirational, it must create yearning for something better (the destination). And for the yearning to be real, we must believe the destination is right for us. Open question – How can we yearn for an IFS when we really can’t know it’s the right destination?

Maps aren’t the territory, but they are a collection of all possible destinations within the design space of the map.  If you have the right map, it contains your destination. And for a long time now, the old paper maps have helped people find their destinations. But on their own maps don’t tell us the direction to drive.  If you have a map of the US and you want to drive to Kansas, in which direction do you drive? It depends. If in California, drive east; if in Mississippi, drive north; if in New Hampshire, drive west; and in Minnesota, drive south. If Kansas is your idealized future state, the map alone won’t get your there.  The direction you drive depends on your location.

GPS has been a nice addition to maps. Enter the destination on the map, ask the satellites to position us globally and it’s clear which way to drive. (I drive west to reach Kansas.) But the magic of GPS isn’t in the electronic map, GPS is magic because it solves the location problem.

Before defining the idealized future state, define your location. It grounds the innovation work in the reality of what is, and people can rally around what is. And before setting the innovation direction with the IFS, define the next problems to solve and walk in their direction.

Image credit – Adrian Brady

By definition, when the work is new there is uncertainty.  And uncertainty can be stressful. But, instead of getting yourself all bound up, accept it.  More than that, relish in it.  Wear it as a badge of honor.  Not everyone gets the chance to work on something new – only the best do.  And, because you’ve been asked to do work with a strong tenor of uncertainty, someone thinks you’re the best.

But uncertainty is an unknown quantity, and our systems have been designed to reject it, not swim in it.  When companies want to get serious they drive toward a culture of accountability and the new work gets the back seat.  Accountability is mis-mapped to predictability, successful results and on time delivery.  Accountability, as we’ve mapped it, is the mortal enemy of new work.  When you’re working on a project with a strong element of uncertainty, the only certainty is the task you have in front of you.  There’s no certainty on how the task will turn out, rather, there’s only the simple certainty of the task.

With work with low uncertainty there are three year plans, launch timelines and predictable sales figures. Task one is well-defined and there’s a linear flow of standard work right behind it – task two through twenty-two are dialed in. But when working with uncertainty, the task at hand is all there is.  You don’t know the next task.  When someone asks what’s next the only thing you can say is “it depends.”  And that’s difficult in a culture of traditional accountability.

An “it depends” Gannt chart is an oxymoron, but with uncertainty step two is defined by step one.  If A, then B.  But if the wheels fall off, I’m not sure what we’ll do next.  The only thing worse than an “it depends” Gantt chart is an “I’m not sure” Gannt chart.  But with uncertainty, you can be sure you won’t be sure.  With uncertainty, traditional project planning goes out the window, and “it depends” project planning is the only way.

With uncertainty, traditional project planning is replaced by a clear distillation of the problem that must be solved.  Instead of a set of well-defined tasks, ask for a block diagram that defines the problem that must be solved.  And when there’s clarity and agreement on the problem that must be solved, the supporting tasks can be well-defined.  Step one – make a prototype like this and test it like that. Step two – it depends on how step one turns out.  If it goes like this then we’ll do that.  If it does that, we’ll do the other.  And if it does neither, we’re not sure what we’ll do.  You don’t have to like it, but that’s the way it is.

With uncertainty, the project plan isn’t the most important thing.  What’s most important is relentless effort to define the system as it is.  Here’s what the system is doing, here’s how we’d like it to behave and, based on our mechanism-based theory, here’s the prototype we’re going to build and here’s how we’re going to test it.  What are we going to do next?  It depends.

What’s next? It depends. What resources do you need? It depends. When will you be done? It depends.

Innovation is, by definition, work that is new.  And, innovation, by definition, is uncertain.  And that’s why with innovation, it depends.  And that’s why innovation is difficult.

And that’s why you’ve got to choose wisely when you choose the people that do your innovation work.

Image credit – Sara Biljana Gaon (off)

Everyone wants to do more innovation.  But how? To figure out what’s going on with their innovation programs, companies spend a lot of time to put projects into buckets but this generates nothing but arguments about whether projects are disruptive, radical innovation, discontinuous, or not.  Such a waste of energy and such a source of conflict.  Truth is, labels don’t matter.  The only thing that matters is if the projects, as a collection, meet corporate growth objectives.  Sure, there should be a short-medium-long look at the projects, but, for the three time horizons the question is the same – Do the projects meet the company’s growth objectives?

To create the causes and conditions for innovation, start with a clear growth objective by geography.  Innovation must be measured in dollars.

Good judgement is required to decide if a project is worthy of resources.  The incremental sales estimates are easy to put together.  The difficult parts are deciding if there’s enough sizzle to cause customers to buy and deciding if the company has the chops to do the work.  The difficulty isn’t with the caliber of judgement, rather it’s insufficient information provided to the people that must use their good judgement.  In shorth, there is poor clarity on what the projects are about. Any description of the projects blurry and done at a level of abstraction that’s too high.  Good judgement can’t be used when the picture is snowy, nor can it be effective with a flyby made in the stratosphere.

To create the causes and conditions for innovation, demand clarity and bedrock-level understanding.

To guarantee clarity and depth, use the framework of novel, useful, successful. Give the teams a tight requirement for clarity and depth and demand they meet it.  For each project, ask – What is the novelty? How is it useful? When the project is completed, how will everyone be successful?

A project must deliver novelty and the project leader must be able to define it on one page.  The best way to do this is to create physical (functional) model of the state-of-the-art system and modify it with the newness created by the project (novelty called out in red).  This model comes in the form of boxes that describe the system elements (simple nouns) and arrows that define the actions (simple verbs).  Think hammer (box – simple noun) hits (arrow -simple verb) nail (box – simple noun) as the state-of-the-art system and the novelty in red – a thumb protector (box) that blocks (arrow) hammer (box).  The project delivers a novel thumb protector that prevents a smashed thumb.  The novelty delivered by the project is clear, but does it pass the usefulness test?

To create the causes and conditions for innovation, demand a one-page functional model that defines and distills down to bedrock level the novelty created by the project.  And to help the project teams do it, hire a good teach teacher and give them the tools, time and training.

The novelty delivered by a project must be useful and the project leader must clearly define the usefulness on one page.  The best way to do this is with a one page hand sketch showing the customer actively using the novelty. In a jobs-to-be-done way, the sketch must define where, when and how the customer will realize the usefulness. And to force distillation blinding, demand they use a fat, felt tip marker. With this clarity, leaders with good judgement can use their judgement effectively. Good questions flow freely. Does every user of a hammer need this? Can a left-handed customer use the thumb guard? How does it stay on? Doesn’t it get in the way? Where do they put it when they’re done? Do they wear it all the time?  With this clarity, the questions are so good there is no escape.  If there are holes they will be uncovered.

To create the causes and conditions for innovation, demand a one-page hand sketch of the customer demonstrating the useful novelty.

To be successful, the useful novelty must be sufficiently meaningful that customers pay money for it.  The standard revenue projections are presented, but, because there is deep clarity on the novelty and usefulness, there is enough context for good judgement to be effective.  What fraction of hammer users hit their thumbs? How often? Don’t they smash their fingers too?  Why no finger protection?  Because of the clarity, there is no escape.

To create the causes and conditions, use the deep clarity to push hard on buying decisions and revenue projections.

The novel, useful, successful framework is a straightforward way to decide if the project portfolio will meet growth objectives.  It demands a clear understanding of the newness created by the project but, in return, provides context needed to use good judgement.  In that way, because projects cannot start without passing the usefulness and successfulness tests, resources are not allocated to unworthy projects.

But while clarity and this level of depth is a good start, it’s not enough.  It’s time for a deeper dive. The project must distill the novelty into a conflict diagram, another one-pager like the others, but deeper.  Like problem definition on steroids, a conflict must be defined in space – between two things (thumb and face of hammer head) – and time (just as the hammer hits thumb).  With that, leaders can ask before-during-after questions.  Why not break the conflict before it happens by making a holding mechanism that keeps the thumb out of the strike zone? Are you sure you want to solve it during the conflict time (when the hammer hits thumb)?  Why not solve it after the fact by selling ice packs for their swollen thumbs?

But, more on the conflict domain at another time.

For now, use novel, useful, successful to stop bad projects and start good ones.

Image credit – Natashi Jay

If you don’t have a problem, there’s no problem. There are no resources without a problem and certainly no focus or momentum.  If you don’t know your problem, stop.  Take time to define your problem using a single page.  Make a sketch or make a block diagram but make it clear.  Make it so the problem description stands on its own. After you’ve defined your problem and someone calls it an “opportunity”, walk away because they can’t help you.  Taking advantage of opportunities is optional, but solving problems is mission critical.  No one worth their salt works on opportunities.  Rock stars solve problems.

After you’ve gnawed on a problem for a month and it hasn’t given in, what do you do?  When you’ve thrown everything at a problem and it still stands tall, what do you do?  When you’ve tried all your tricks and the intractable problem is still blocking an already overdue product launch, what do you do?  What you do is find someone who is unafraid trade an intractable problem for a solvable one, someone who will courageously give ground with the hope of opening up new design space, someone who will unabashedly take an anti-conventional (and hopefully controversial) approach.  What you do is find a rock star.

Intractable problems are not usually intractable; rather, intractable problems are either poorly-defined problems or are the wrong problem altogether.  Either way, it takes someone with courage, usually an outsider, to redefine the problem or see it differently.  But because of pride, an outsider can be brought in only after the team has exhausted all other possibilities.  Unless there’s a problem with the problem solving team (they can’t solve the problem), there’s no problem.  And without a problem, the team won’t accept help from an outsider.

At the rodeo when the cowboy is bucked off the raging bull, the cowboy runs away from the bull but the rodeo clown runs toward the bull to distract it.  Like the rodeo clown, the problem solving rock star runs toward raging problems at full tilt.  The rock star puts it all on the line as she grabs the problem by the scruff of the neck, wrestles it to the ground and hog ties it.  There’s no shyness, just well-practiced technique wrapped in implicit knowledge.  With courage and a cloud of dust, it’s no-holds-barred problem solving until the problem gives it up. Nothing is sacred, no assumptions go unchallenged, and no details are too small to ignore.  Like rodeo clowns, rock stars know their work looks funny from the outside, but they don’t care.  All they care about is solving the problem at hand. Right here, right now.

Before your next intractable problem, take a minute to scan your organization for the special people who have the courage to run toward even the most difficult problems.  Don’t be fooled by titles, positional power or how they dress.  Look deeply because like rodeo clowns, your magical problem solvers may not look the part on the outside.

Image credit – Ed Schipul

The 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

Immediately after there’s an elegant solution to a previously intractable problem, the solution is obvious to others.  But, just before the solution those same folks said it was impossible to solve.  I don’t know if there’s a name for this phenomenon, but it certainly causes hart burn for those brave enough to take on the toughest problems.

Intractable problems are so fundamental they are no longer seen as problems.  Over the years experts simply accept these problems as constraints that must be complied with.   Just as the laws of physics can’t be broken, experts behave as if these self-made constraints are iron-clad and believe these self-build walls define the viable design space.  To experts, there is only viable design space or bust.

A long time ago these problems were intractable, but now they are not.  Today there are new materials, new analysis techniques, new understanding of physics, new measurement systems and new business models.. But, they won’t be solved.  When problems go unchallenged and constrain design space they weave themselves into the fabric of how things are done and they disappear.   No one will solve them until they are seen for what they are.

It takes time to slow down and look deeply at what’s really going on.  But, today’s frantic pace, unnatural fascination with productivity and confusion of activity with progress make it almost impossible to slow down enough to see things as they are.  It takes a calm, centered person to spot a fundamental problem masquerading as standard work and best practice.  And once seen for what they are it takes a courageous person to call things as they are.  It’s a steep emotional battle to convince others their butts have been wet all these years because they’ve been sitting in a mud puddle.

Once they see the mud puddle for what it is, they must then believe it’s actually possible to stand up and walk out of the puddle toward previously non-viable design space where there are dry towels and a change of clothes.  But when your butt has always been wet, it’s difficult to imagine having a dry one.

It’s difficult to slow down to see things as they are and it’s difficult to re-map the territory.   But it’s important.  As continuous improvement reaches the limit of diminishing returns, there are no other options.  It’s time to solve the intractable problems.

Image credit – Steven Depolo