Options are normally the two or three that come to mind first — and they sit close to the current state and to concrete demands. This tool builds the whole space instead: it abstracts attributes from real entities of a class, opens up the values each could take, and composes configurations nobody had yet.
Collection is unstructured on purpose and structured afterwards; the utopia is set before the optimum; a need may be held by several stakeholders and the configuration is assessed against those needs; and values that cannot stand together are refused rather than argued about.
MORPHΩN — from μορφωτικόν, morphōtikón, what pertains to shaping; μορφή is the form a thing has taken. The tool forms: it takes the entities that already exist, finds the attributes they share, opens up the values those attributes could take, and builds from them a configuration nobody had yet.
It is stakeholder-centric by construction. The method was first called SCMC — stakeholder-centric morphological configurations — and that is still what it does. The objective a configuration is measured against is not yours: it is what you set so that stakeholders’ needs are satisfied and their behaviour turns favourable to you.
Strategy runs in four phases: clarification, formation, transformation, operation. This tool belongs to the second. It presumes the question is settled — what may change, what may not, and what is actually wrong — and it produces the options that answer it.
As a working tool, in the hands of a trained strategist — the senior strategist of the entity, say — who knows the method and drives it alone or with a small team.
Or, and this is where it is worth most, in a workshop moderated by such a specialist, or by us. Because the tool runs online, that workshop works over a collaboration platform (e.g. Teams®) as well as it does in a room.
The operating steps of each page stand on the page itself, under What this does and how to use it. What follows here is what those pages cannot say for themselves.
The utopia honours what cannot be changed by anyone — law, nature, what stakeholders actually need — and ignores only what cannot be changed by you: your capabilities, your resources, your history. It is a thought experiment with rules, and its function is to show what the optimum is an approximation of.
Some values cannot stand together: a tent at the north pole. Mark the pair and the tool refuses any configuration containing both. This is what keeps a large box workable — the arithmetic of combinations is brutal, and most of what it produces is impossible.
It forms configurations and records their assessment. It does not decide between them, does not value them in money, and does not plan the transformation to reach them — those follow, with other instruments. Nor does it lay relations and axioms over the classification, beyond the pairs of values it refuses, and it forms no archetypes; both are later steps, with instruments of their own.
This tool is a synthesis. The morphological method is Fritz Zwicky's; the stakeholder-centric reading of it, the utopia–optimum distinction and the naming discipline are the work of dsc Strategy Consulting. The foundations are named on the rights page.
| Term | Meaning here |
|---|---|
| Set | The entity class under analysis — the genus, not your own entity. |
| Actual | A concrete entity of the set, at a point in time. |
| Property | What the room says of an actual, in its own words, before it is read as an attribute holding a value. |
| Attribute | A category that can hold different values, named as an accessible cause. |
| Value | One variant an attribute can take. |
| Cluster | A group of attributes or of clusters, with a rank — sub · micro · meso · macro · supra. Used when a level carries more than seven. |
| Configuration | One value chosen per selected attribute. |
| Utopia | The configuration that would best satisfy, ignoring your own limits. |
| Optimum | The utopia applied to what you actually have. |
| Stakeholder | A role that has to be satisfied — never a person. |
| Specific need | Between the abstract basic need and the volatile demand. One need may be held by several stakeholders. |
| Incompossible | Two values that cannot stand in one configuration. |
No server, no account, no transmission. The tool runs in your browser and your case stays there — which is why it can be used on material a client would never put in a cloud.
It follows that a private window forgets everything when it closes, and that clearing your browser data clears the case with it. Save file keeps a copy; the exports take the result out.
The entity class, not your entity. Distance is the point.
Working one level up buys intellectual and emotional distance, and it lets the attributes be found once and reused for every member of the set — including competitors.
You now, others now, both in the past, and ones you only imagine. Each is raw material for abstraction — an imagined entity works as well as a real one.
Nobody writes a universal. A card says a particular — something to keep, to stop, to start — and the universal it instances has to be named, out loud, with the room. That is the hard step of the whole method, and it is done before anything is grouped.
Now the walls. A cluster opens where it stands; the arrow puts it to the front and everything else leaves the screen. Group what is there — never go back and bend a universal to fit a group you liked.
Attributes arrive here from Abstraction, and they can also be typed straight in. A room that already thinks in universals starts on this page, sets the values in Exploration, and comes back to group them once there is something to group. Clustering is not a step that has to happen first — every level is built by dragging one box into another, whenever the shape becomes clear.
Every group is a cluster; its rank says where it stands. The ladder runs sub · micro · meso · macro · supra, and a group is given its rank when it is named — nothing is computed from the shape. Split a microcluster and the new level below it is a subcluster; the microcluster keeps its name.
The values already seen in the actuals are there. Add the ones nobody has taken yet — and the null value where doing without is a real option.
An attribute can be named here too, with its values under it in the same breath — which is how a room says them. Grouping comes after, on Structure, once there is a range to group over.
The classification as it now stands. Choose a level, then look one step up from it or one step down. Moving an element sideways changes what it belongs to — that is segmentation. Changing its level moves it up or down — that is hierarchization. They are two gestures and this is where they are told apart.
What stands beside your level is read off the classification, not off the ladder: the boxes are the parents that are actually there, each labelled with its own rank. An attribute has nothing below it and a supracluster nothing above. It becomes an ontology once relations and axioms are laid over it — that is a later step, and not this page.
Select the attributes whose value most changes satisfaction. More than seven at one level is not too many — it is unstructured: group them into a cluster instead of dropping them.
Selecting the attribute said this dimension matters. This says which of its values the room will actually consider. A value taken out stays written down — it is out of play, not deleted, and it can come back the moment somebody argues for it.
Click a cell to set it in the configuration you are working on. utopia optimum ✕ marks a value that cannot stand with one already set
Two values that cannot stand together. Mark the pair once and no configuration will hold both.
Who has to be satisfied. Never a person, always a role — not your CFO but representative of the providers of capital. That is the abstraction that gets a room out of its own building, and it is what lets one classification serve the next entity of the same set without a confidentiality question.
One per line, or paste a block. They appear as boxes here until you put them in a cluster below.
Name a microcluster, then drag stakeholders into it. More than seven in one place is not too many — it is unstructured.
One level up: name a mesocluster and drag microclusters into it.
The top level here — investors, customers, employees and their like. Drag mesoclusters into it.
What each of them needs. A specific need sits between the abstract basic need and the volatile demand: predictable cash flow, not security and not pay us in thirty days.
Enter a need here for one stakeholder. That a second stakeholder holds the same need is said on the Allocation page — never by entering it twice, which would make one need into two.
Name a microcluster, then drag needs into it.
One level up: name a mesocluster and drag microclusters into it.
The top level here — investors, customers, employees and their like. Drag mesoclusters into it.
Who shares which need. Drag a need onto another stakeholder and it is copied — the one it came from keeps it, because a need held by two is one need held twice and not two needs. An investor wants growth and low volatility of the entity's returns; a supplier wants exactly that, for their own firm.
Drawn at the highest level there is: a supercluster hides its clusters, a cluster hides its needs. Cluster on the two pages before this one and this one stays readable.
This is the ground, not an extra. Needs → satisfaction → behaviour → success: the objective below is not yours, it is what you set so that stakeholders behave in a way that is favourable to you. They are named on the Stakeholders page, their needs on Needs, and who shares which need on Allocation — not here, because identification is its own work.
The two questions that send you back: satisfaction sends you to value setting, feasibility sends you to selection.
Group by whichever axis shares least across its members: by stakeholder while groups share few needs, by need while needs share few stakeholders. Click a field to mark it and to write the remark that belongs to it.
This tool is a synthesis. It was derived from an analysis of the works named below and combined with development of our own. The morphological box is Fritz Zwicky's. The stakeholder-centric reading of it, the utopia–optimum distinction, the naming discipline and the hierarchisation rule are the work of dsc Strategy Consulting. We claim neither the foundations nor the established techniques built on them — they are named and attributed here. What we claim is the synthesis, and the moves the literature does not contain. This page shows what was inherited from whom, and what was developed here.
The morphological method
Classification, and the business model as its frame
Stakeholders and their needs
Structured ideation
Iteration, and the loop back
Organisational configuration
Use permitted, redistribution and resale prohibited.
Provided without contractual obligation. The tool computes and displays; it does not advise and does not decide.