Design: more of a story than a process

In the beginning, there is no problem.

The problem might exist, but it is unknown.

Then someone suspects there might be a problem.

And someone is concerned.

So someone starts to observe and analyse it.

They begin to better understand the problem;

And they discover that the problem comprises many problems!

The concern grows;

And turns into resolve.

So someone observes and analyses the many component problems.

They begin to better understand them and how they’re related;

And the people they impact and how they’re impacted.

And whether anyone else is seeking to solve them.

They establish which of the component problems are the most important;

And which they won’t even try and solve.

They look at the component problems from various perspectives;

And at different levels of abstraction;

And through various frames, lenses and filters.

They recognise similarities with other problems that have been solved;

And they consider whether the solutions to these problems might apply.

They recognise differences with similar problems that have been solved;

And they consider what different solutions might resolve these.

They select solutions to the most important component problems.

They synthesise the component solutions;

And record the results.

They select solutions to the other component problems;

And synthesise, integrate, combine or otherwise incorporate these;

And update their records.

They’ve designed a solution;

But not necessarily the solution;

And they’ve not yet solved the problem, so ...

They show the designed solution to those resolved to solving the problem.

They estimate how well the implemented solution might solve the problem;

And how much it’ll cost to implement;

And what previously unforeseen consequences it might create;

And whether further work might yield a better solution.

They evaluate their options;

And decide whether to implement the solution as designed;

Or cease work on the problem;

Or commission further work …

To better describe how this solution might solve the problem;

Or refine specific qualities of the designed solution;

Or synthesise different permutations of component solutions;

Or consider a different set of component problems.

And establish which of the component problems are the most important;

And which they won’t even try and solve.

And so on;

And so on;

Until there is no further work to do;

And they all lived happily ever-after …

… or nobody compromised and nothing got resolved.

After all, it’s a story, not a fairytale!

----------

Ben is a Business Architect and designer of business and operating models, solutions and services. He's available to hire on a contract basis, but he'll also consider retainers and advisory positions. 

You can read his other posts here, including: 'Can I be a [Something] Architect too?' and 'Lessons in business architecture from Gaudí'.