Archive for the ‘Fundementals’ Category

To improve productivity, it’s time to set limits.

The race for productivity is on. And to take productivity to the next level, set limits.

To reduce the time wasted by email, limit the number of emails a person can send to ten emails per day. Also, eliminate the cc function. If you send a single email to ten people, you’re done for the day.  This will radically reduce the time spent writing emails and reduce distraction as fewer emails will arrive. But most importantly, it will help people figure out which information is most important to communicate and create a natural distillation of information. Lastly, limit the number of word in an email to 100. This will shorten the amount of time to read emails and further increase the density of communications.

If that doesn’t eliminate enough waste, limit the number of emails a person can read to ten emails per day.  Provide the subject of the email and the sender, but no preview.  Use the subject and sender to decide which emails to read.  And, yes, responding to an email counts against your daily sending quota of ten.  The result is further distillation of communication. People will take more time to decide which emails to read, but they’ll become more productive through use of their good judgement.

Limit the number of meetings people can attend to two per day and cap the maximum meeting length to 30 minutes. The attendees can use the meeting agenda, meeting deliverables and decisions made at the meeting to decide which meetings to attend. This will cause the meeting organizers to write tight, compelling agendas and make decisions at meetings. Wasteful meetings will go away and productivity will increase.

To reduce waiting, limit the number of projects a person can work on to a single project.  Set the limit to one. That will force people to chase the information they need instead of waiting. And if they can’t get what they need, they must wait. But they must wait conspicuously so it’s clear to leaders that their people don’t have what they need to get the project done. The conspicuous waiting will help the leaders recognize the problem and take action.  There’s a huge productivity gain by preventing people from working on things just to look busy.

Though harsh, these limits won’t break the system. But they will have a magical influence on productivity. I’m not sure ten is the right number of emails or two is the right number of meetings, but you get the idea – set limits.  And it’s certainly possible to code these limits into your email system and meeting planning system.

Not only will productivity improve, happiness will improve because people will waste less time and get to use their judgement.

Everyone knows the systems are broken. Why not give people the limits they need and make the productivity improvements they crave?

Image credit –  XoMEoX

Innovate like a professional with the Discovery Burst Event.

Recreational athletes train because they enjoy the activity and they compete so they can tell themselves (and their friends) stories about the race. Their training routines are discretionary and their finish times are all about bragging rights. Professional athletes train because it’s their job. Their training is unpleasant, stressful and ritualistic. And it’s not optional. And their performance defines their livelihood. A slow finish time negatively impacts their career. With innovation, you have a choice – do you want to do it like a recreational athlete or like a professional? Do you want to do it like it’s discretionary or like your livelihood depends on it?

Like with the professional athlete, with innovation what worked last time is no longer good enough.  Innovation demands we perform outside our comfort zone.

Goals/Objectives are the key to performing out of our comfort zone. And to bust through intellectual inertia, one of the most common business objectives is a goal to grow revenue. “Grow the top line” is the motto of the professional innovator.

To deliver on performance goals, coaches give Strategic Guidance to the professional athlete, and it’s the same for company leaders – it’s their responsibility to guide the innovation approach. The innovation teams must know if their work should focus on a new business model, a new service or a new product. And to increase the bang for the buck, an Industry-First approach is recommended, where creation of new customer value is focused within a single industry. This narrows the scope and tightens up the work. The idea is to solve a problem for an industry and sell to the whole of it.  And to tighten things more, a Flagship Customer is defined with whom a direct partnership can be developed.  Two attributes of a Flagship Customer – big enough to create significant sales growth and powerful enough to pull the industry in its wake.

It’s the responsibility of the sales team to identify the Flagship Customer and broker the first meeting.  At the meeting, a Customer-Forward approach is proposed, where a diverse team visits the customer and dives into the details of their Goals/Objectives, their work and their problems. The objective is to discover new customer outcomes and create a plan to satisfy them.  The Discovery Burst Event (DBE) is the mechanism to do the work  It’s a week-long event where marketing, sales, engineering, manufacturing and technical services perform structured interviews to get to the root of the customer’s problems AND, in a Go-To-The-Work way, walk their processes and use their eyeballs to discover solutions to problems the customer didn’t know they had.  The DBE culminates with a report out to leaders of the Flagship Company where new customer outcome statements are defined along with a plan to assess the opportunities (impact/effort) and come back with proposals to satisfy the most important outcome statements.

After the DBE, the team returns home and evaluates and prioritizes the opportunities.  As soon as possible, the prioritization decisions are presented to the Flagship Customer along with project plans to create novel solutions.  In a tactical sense, there are new opportunities to sell existing products and services.  And in a strategic sense, there are opportunities to create new business models, new services and new products to reinvent the industry.

In the short term, sales of existing products increase radically.  And in the longer term, where new solutions must be created, the Innovation Burst Event (IBE) process is used to quickly create new concepts and review them with the customer in a timely way. And because the new concepts solve validated customer problems, by definition the new concepts will be valued by the customer. In a Customer-Forward way, the new concepts created by the IBE are driven by the customer’s business objectives and their problems.

This Full Circle approach to innovation pushes everyone out of their comfort zones to help them become professional innovators. Company leadership must stick out their necks and give strategic guidance, sales teams must move to a trusted advisor role, engineering and marketing teams must learn to listen to (and value) the customer’s perspective, and new ways of working – the Discovery Burst Event (DBE) and Innovation Burst Event (IBE) – must be embraced.  But that’s what it takes to become professional innovators.

Innovation isn’t a recreational sport, and it’s time to behave that way.

Image credit – Lwp Kommunikáció

The WHY and HOW of Innovation

Innovation is difficult because it demands new work. But, at a more basic level, it’s difficult because it requires an admission that the way you’ve done things is no longer viable. And, without public admission the old way won’t carry the day, innovation cannot move forward. After the admission there’s no innovation, but it’s one step closer.

After a public admission things must change, a cultural shift must happen for innovation to take hold. And for that, new governance processes are put in place, new processes are created to set new directions and new mechanisms are established to make sure the new work gets done.  Those high-level processes are good, but at a more basic level, the objectives of those process areto choose new projects, manage new projects and allocate resources differently. That’s all that’s needed to start innovation work.

But how to choose projects to move the company toward innovation? What are the decision criteria? What is the system to collect the data needed for the decisions? All these questions must be answered and the answers are unique to each company. But for every company, everything starts with a top line growth objective, which narrows to an approach based on an industry, geography or product line, which then further necks down to a new set of projects. Still no innovation, but there are new projects to work on.

The objective of the new projects is to deliver new usefulness to the customer, which requires new technologies, new products and, possibly, new business models. And with all this newness comes increased uncertainty, and that’s the rub. The new uncertainty requires a different approach to project management, where the main focus moves from execution of standard tasks to fast learning loops. Still no innovation, but there’s recognition the projects must be run differently.

Resources must be allocated to new projects. To free up resources for the innovation work, traditional projects must be stopped so their resources can flow to the innovation work. (Innovation work cannot wait to hire a new set of innovation resources.)  Stopping existing projects, especially pet projects, is a major organizational stumbling block, but can be overcome with a good process. And once resources are allocated to new projects, to make sure the resources remain allocated, a separate budget is created for the innovation work. (There’s no other way.) Still no innovation, but there are people to do the innovation work.

The only thing left to do is the hardest part – to start the innovation work itself. And to start, I recommend the IBE (Innovation Burst Event). The IBE starts with a customer need that is translated into a set of design challenges which are solved by a cross-functional team.  In a two-day IBE, several novel concepts are created, each with a one page plan that defines next steps.  At the report-out at the end of the second day, the leaders responsible for allocating the commercialization resources review the concepts and plans and decide on next steps. After the first IBE, innovation has started.

There’s a lot of work to help the organization understand why innovation must be done. And there’s a lot of work to get the organization ready to do innovation. Old habits must be changed and old recipes must be abandoned. And once the battle for hearts and minds is won, there’s an equal amount of work to teach the organization how to do the new innovation work.

It’s important for the organization to understand why innovation is needed, but no customer value is delivered and no increased sales are booked until the organization delivers a commercialized solution.

Some companies start innovation work without doing the work to help the organization understand why innovation work is needed. And some companies do a great job of communicating the need for innovation and putting in place the governance processes, but fail to train the organization on how to do the innovation work.

Truth is, you’ve got to do both. If you spend time to convince the organization why innovation is important, why not get some return from your investment and teach them how to do the work? And if you train the organization how to do innovation work, why not develop the up-front why so everyone rallies behind the work?

Why isn’t enough and how isn’t enough. Don’t do one without the other.

Image credit — Sam Ryan

How To Reduce Innovation Risk

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

See differently to solve differently.

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

Innovation and the Mythical Idealized Future State

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

Full Circle Innovation

It’s not enough to sell things to customers, because selling things is transactional and, over time, transactional selling deteriorates into selling on price. And selling on price is a race to the bottom.

Sales must move from transactional to relational, where people in the sales organization become trusted advisers and then something altogether deeper. At this deeper level of development, the sales people know the business as well as the customer, know where the customer wants to go and provide unique perspective and thoughtful insight.  That’s quite a thing for sales, but it’s not enough.  Sales must become the conduit that brings the entire company closer to the customer and their their work.

When the customer is trying to figure out what’s next, sales brings in a team of marketing, R&D and manufacturing to triangulate on the future.  The objective is to develop deep understanding of the customer’s world.  The understanding must go deeper than the what’s.  The learning must scrape bottom and get right down to the bedrock why’s.

To get to bedrock, marketing leads learning sessions with the customer.  And it all starts by understanding the work.  What does the customer do? Why is it done that way? What are the most important processes? How did they evolve? Why do they flow the way they do? These aren’t high-level questions, they are low-level, specific questions, done in front of the actual work.

The mantra – Go to the work.

When the learning sessions are done well, marketing includes experts in manufacturing and R&D.  Manufacturing brings their expertise in understanding process and R&D brings their expertise in products and technologies.  And to understand the work the deepest way, the tool of choice is the Value Stream Map (VSM).

Cross-organization teams are formed (customer, sales, marketing, manufacturing, and R&D) and are sent out to create Value Steam Maps of the most important processes.  (Each team is supported by a VSM expert.)  Once the maps are made, all the teams come back together to review the them and identify the fundamental constraints and how to overcome them.  The solutions are not limited to new product offerings, rather the solutions could be training, process changes, policy changes, organizational changes or business model changes.

Not all the problems are solved in the moment.  After the low hanging fruit is picked, the real work begins.  After returning home, marketing and R&D work together to formulate emergent needs and create new ways to meet them.  The tool of choice is the IBE (Innovation Burst Event).

To prepare for the IBE, marketing and R&D formalize emergent needs and create Design Challenges to focus the IBE teams.  Solving the Design Challenges breaks the conflicts creates novel solutions that meet the unmet needs.  In this way, the IBE is a pull process – customer needs create the pull for a solution.

The IBE is a one or two-day event where teams solve the Design Challenges by building conceptual prototypes (thinking prototypes).  Then, they vote on the most interesting concepts and create a build plan (who, what, when).  The objective of the build plan is to create a Diabolically Simple Prototype (DSP), a functional prototype that demonstrates the new functionality. What makes it diabolical is quick build time.  At the end of the IBE is a report out of the build plan to the leader who can allocate the resources to execute it.

In a closed-loop way, once the DSP is built, sales arranges another visit to the customer to demonstrate the new solution.  And because the prototype designed to fulfill the validated customer need, by definition, the prototype will be valuable to the customer.

This full circle process has several novel elements, but the magic is in the framework that brings everyone together.  With the process, two companies can work together effectively to achieve shared business objectives.  And, because the process brings together multiple functions and their unique perspectives, the solutions are well-thought-out and grounded in the diversity of the collective.

Image credit – Gerry Machen

Why not start?

startIt doesn’t matter where the journey ends, as long as it starts.

After starting, don’t fixate on the destination, focus on how you get there.

A long project doesn’t get shorter until you start. Neither does a short one.

Start under the radar.

When a project is too big to start, tear off a bite-sized chunk, chew it and swallow.

Sometimes slower is faster, but who cares. You’ve started.

If you can’t start, help some else start. You’ll both be better for it.

Fear blocks starting. But if you’re going to be afraid, you might as well start.

The only way to guarantee failure is to fail to start.

After you start, tell your best friend.

When starting, be clear on your location and less clear on the destination.

You either start or you don’t. With starting, there’s no partial credit.

Don’t start unless you’re going to finish.

Starting is scary, right up until you start.

The best way to free up time to start a good project is to stop a bad one.

Sometimes it’s best to stop starting and start finishing.

You don’t need permission to start. You just need to start.

Start small. If that doesn’t work, start smaller.

In the end, starting starts with starting.

And if you don’t start you can’t finish.


Image credit — jakeandlindsay

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

Celebrating Seven Years of Blog Posts – what I’ve learned about writing.

%desxToday marks seven years of weekly blog posts.  Here’s what I’ve learned so far:

When you can write about anything, what you choose tells everyone what you’re about.

Sometimes you’ve got to start writing to figure out what you have to say.

Some people think semicolons are okay; others don’t like to show off.

When you don’t want to write and you write anyway, you feel good when you’re done.

Use short sentences. Use fewer words.

Writing is the best way to learn you don’t know what you’re talking about.

Writing is a good way to have a deep conversation with yourself.

Worrying about what people will think is the surest way to write like crap.

Writing improves by writing.

When the topic comes slowly, start writing. And when the words don’t come at all, repeat.

If you don’t know what you are talking about before you start writing, no worries. You’ll know when you’re done.

When you have nothing to say it’s because what you have to say is too personal share.

For me, writing is learning.


Image credit David Kutschke


Make it work.

square-pegIf you think something can’t be done, it won’t get done.  And if you think it may be possible, or is possible, it may get done.  Those are the rules.

If an expert says it will work, it will work.  If they say it won’t work, it might.  Experts can tell you will work, but can’t tell you what won’t.

If your boss tells you it won’t work, it might. Give it a try.  It will be fun if it works.

If you can’t make it work, make it worse and then do the opposite.

If you can’t explain the problem to your young kids, you don’t understand the situation and you won’t make it work.

If something didn’t work ten years ago, it may work now. Technology is better and we’re smarter.  More likely it would have worked ten years ago if they ran more than one crude experiment before they gave up.

If you can’t draw a one page sketch of the problem, it may never work.

If you can’t make it work, put it down for three days. Your brain may make it work while you’re sleeping.

If you don’t know the problem, you can’t make it work.  Be sure you’re trying to solve the right problem.

If your boss tells you it will work, it might.  If they tell you how to make it work, let them do it.

If none of your attempts have been fruitful and you’re out of tricks, purposely make one performance attribute worse to free up design space. That may work.

If you don’t know when the problem occurs, you don’t know much. Your solutions won’t work.

If you tried everything and nothing worked, ask someone for help whose specialty in an unrelated area.  They may have made it work in a different domain.

If you think everyone in the group understands the problem the same way, they don’t.  There’s no way they’ll agree on the best way to make it work. Don’t wait for consensus.

If you don’t try, that’s the only way to guarantee it won’t work.

Image credit – Simon Greig



Mike Shipulski Mike Shipulski
Subscribe via Email

Enter your email address:

Delivered by FeedBurner