Your Training Partner
Techniques Toolbox
Diagram of Möbius Ideation. On the left, the resource inventory: people with their skills and workload, equipment and tools with their current use. Below it, the project and team constraints lead to what is lacking. Resources and gaps feed the step 7 questions: what can be changed, what or who can be stretched, what or who can fulfil unaddressed needs, how to tackle the remaining needs, which trade-offs arise and how to manage them. On the right come the reassignment options, each with its trade-off. A need with no internal solution is raised to the sponsor.

Möbius Ideation

Möbius Ideation is an ideation workshop in which a team tries to get more value from the resources it already has: its people and their skills, its equipment and its tools. Two to five people record these resources and the project's constraints. They then ask five questions of each resource. Three ask what can change, do more or cover a need. Two ask which needs remain unmet and what trade-off each change costs. The workshop delivers reassignment options. George W. Anderson describes the technique in Design Thinking for Tech (2023). The name comes from the Möbius strip.

Goal

Möbius Ideation deals with a shortfall that the organisation will not close in time, because the budget is set, hiring is frozen or a purchase takes months. Anderson counts it among the ways to avoid waiting for extra resources and gives it one aim: "more value at the same cost". The team keeps its obligations, its budget, its schedule and its headcount. It gets more out of the people, equipment and tools it already has.

The workshop produces reassignment options. Each option states which resource changes its use, which need it covers and what trade-off it costs. Whoever allocates the resources chooses the options to implement: the project manager, the sponsor or the line manager.

Usage

When to use it

  • Frozen budget or headcount: no extra resource will arrive before the deadline.
  • Project waiting for reinforcements: the workshop looks for who covers the need while a hire or a purchase is under way.
  • Task without an owner: nobody is in charge of onboarding newcomers or of communication to stakeholders.
  • Underused equipment or tool: a test environment, a licence or a room serves a single activity.
  • Team that talks openly about its workload: the question "who can be stretched?" demands frank answers in front of colleagues.
  • Known workload for each person: a schedule or a tracking tool shows who works on what and at what percentage.
  • Remote team: the workshop runs as a video call with a shared whiteboard.

When not to use it

  • Team already overloaded: an extended role leads to burnout. Reduce the scope through prioritisation instead.
  • Required skill missing from the team: no reassignment creates it. Run a make-or-buy analysis.
  • Problem whose cause is not a lack of resources: look for that cause first with root cause analysis.

Description

The strip and what it stands for

A Möbius strip is a band closed after a half twist. It has a single side: a path along the strip crosses both faces of the original band before it returns to its starting point. Anderson takes the idea behind the technique from it: a resource often does less than it could. Examples are a skill that the role leaves unused and a tool kept for a single use. Anderson adds that the analogy serves only to view resources in a new way.

He relates the technique to Good Enough Thinking, which he describes in the same chapter. Good Enough Thinking starts from the limits of scope, schedule and budget to set the level of quality that is sufficient. Möbius Ideation starts from the same limits to make better use of the resources. Anderson speaks of ideation through a "lens of efficiency".

Participants and duration

Anderson calls for two to five people and sixty minutes per problem. A complex problem can extend the exercise. The participants are the team members, the project manager and the business analyst. They know the resources under discussion. One of them facilitates and writes on the board. The person who allocates the resources attends the end of the session or receives the options afterwards.

The steps

The steps are Anderson's. The facilitation instructions that go with them are our reading. In steps 1 to 6 the team draws up two lists: the resources and the gaps. It tests the resources against the gaps in step 7.

Resources (steps 1 and 2)
People and roles: skills, workload
Equipment: current use
Tools: current use
Constraints (steps 3 to 6)
Project constraints
Team constraints
Why the constraint holds
What is lacking
Step 7
a. What can be changed?
b. What or who can be stretched?
c. What or who can fulfill unaddressed needs?
d. How might the team tackle remaining needs?
e. Which trade-offs arise and how to manage them?
Reassignment options
Option
Trade-off and mitigation
Option
Trade-off and mitigation
Option
Trade-off and mitigation
Remaining need: raised to the sponsor
The team inventories its resources in steps 1 and 2. In steps 3 to 6, it works out from the constraints what is lacking. In step 7, it tests each resource against the gaps with five questions. Each option carries its trade-off.
  1. Frame. The team meets, names the project and states the problem. The facilitator has it written in concrete terms: "the regression tests for the April release have no owner".
  2. Inventory the people. The team lists the human resources available today, by person or by role. For each one, it notes the skills, capabilities, experience and qualifications. Anderson limits this list to people. Yet his seventh step covers "each person and each resource". So the team adds the equipment and tools with their current use. It also notes each person's workload. Without the workload, the question "who can be stretched?" gets a guessed answer.
  3. Record the project's constraints. The team notes the conditions the project is under, such as a fixed budget or an imposed go-live date.
  4. Record the team's constraints. It notes the team's own, such as no travel or partial availability.
  5. State why each constraint holds. For each constraint, the team notes why the situation is difficult or impossible to change. A constraint without a written reason is often a habit. The team records it as a question for the person who set it and respects it during the workshop.
  6. State what is lacking. For each constraint, the team notes what the project or the team lacks. These gaps are the unaddressed needs of step 7.
  7. Test each resource against the gaps. The team takes each person and each resource connected to the situation. It discusses Anderson's five questions within today's constraints.

Anderson gives steps 3 to 6 no format. A table with one row per constraint groups them. A Lausanne insurer is replacing its claims management application. Its project team of four holds the session on 12 January.

Constraints table for steps 3 to 6. Proposed format and invented example.
ConstraintOriginWhy the constraint holdsWhat is lacking
Budget of CHF 420'000ProjectIn November, management approved an annual budget that excludes training. No top-up during the financial year.Training for the 40 claims handlers
Go-live on 1 AprilProjectThe maintenance contract for the old application expires on 31 March.Time for regression testing
Tester at 50%TeamHe also works on the billing project.Checking the migration of the 180'000 claim files
No hiring before JulyTeamManagement has frozen headcount.Support for the claims handlers after go-live

The step 7 questions

The questions are Anderson's. The notes that follow them are our reading.

  1. "What can be changed?" An assignment, a schedule, a way of working or the use of a tool.
  2. "What or who can be stretched?" A person takes on an additional role. A tool serves a second use.
  3. "What or who can fulfill unaddressed needs?" The team tests the inventory of step 2 against the gaps of step 6.
  4. "How might the team tackle any remaining unaddressed needs?" The team raises with the sponsor each need that no resource covers and the date on which it blocks the project.
  5. "What are the trade-offs, and how might they be managed?" Anderson names burnout, role complexity and blurred accountability.

Anderson's examples are people who take on more roles. He places the gain in onboarding, communication, management and stakeholder relations.

Pitfalls

The stretch that turns into overload. Overload starts at question (b). An option that adds a task to a person names the offset: the task that person drops or an end date. Without the offset, the option amounts to overtime. The team also sets a review date on which it checks the workload of the people concerned.

Diluted accountability. A reassigned task keeps a single owner. When a developer takes over communication to users, the team states who answers for it to the sponsor. It updates the RACI matrix after the session.

The person discussed in their absence. An option that changes someone's role is adopted only with their consent. The person takes part in the session. Otherwise, the facilitator consults them before the decision.

The inventory by guesswork. Skills and workloads estimated from memory produce wrong options. The team checks workload against the schedule and skills against the competency framework where one exists.

The metaphor sold as a result. Anderson writes that the strip offers "potentially twice the value" of an ordinary loop. The team presents its options and their trade-offs to the sponsor without promising doubled value.

The name that puts people off. In the same chapter, Anderson tells of a team that rejected the help on offer because the names of unfamiliar techniques scared it off. He advises describing the process and its outcome rather than the name. So the facilitator announces "an hour to see how the current team can cover the tests".

AI considerations

A language model prepares the inventory. From the role descriptions and the project plan, it draws up a first list of the skills of each role and the uses of each tool. This list omits the skills that the role leaves unused. Yet the team looks for those skills in step 7. Each person completes their own row. During the session, the model proposes candidate resources for each gap. This widens question (c). After the session, it writes up the notes in the options register.

It lacks what the participants know: each person's actual workload, their wishes, the tensions in the team and a person's tolerance for an extra role. The team settles question (e) with the people concerned, never through a ranking of colleagues produced by the model.

The inventory holds personal data: skills, workload and sometimes absences. In a team of four, a role identifies a person. A team that replaces names with roles therefore does not anonymise the data. The team submits the inventory to a service that the organisation has approved. For any other service, it removes the workload and the absences.

Examples

The options register shows the result of step 7. Each option carries the question that produced it and the trade-off it costs. The case continues with the insurer from the constraints table.

Register of reassignment options. Proposed format and invented example.
ResourceCurrent useOptionQuestionTrade-off and mitigation
Business analystWrites the requirements and the acceptance scenariosBuilds the training for the claims handlers from the acceptance scenarios(c)More complex role. The product owner takes over the acceptance criteria until 1 April.
HR department's e-learning platformAnnual mandatory trainingHosts the training modules for the new application(b)HR keeps control of the platform. A written agreement grants access until June.
Senior developerDevelops the interfaces with accountingAutomates the regression tests for the twelve high-risk claim workflows(a)Two features slip by one sprint. The sponsor accepts the slip in writing.
Experienced claims handlerHandles claims and validates the mock-upsAnswers her colleagues' questions for the six weeks after go-live(b)Risk of burnout. Her manager takes 20% of her caseload off her for that period.
No internal resource-Checking the migration of the 180'000 claim files(d)Raised to the sponsor. Without a decision by 15 February, go-live slips.

The last row is part of the result. Question (d) handles the need that no internal resource covers. The register names it with the date on which it blocks the project.

Visualisations

The diagram of the steps shows how the resource inventory and the gaps that the team works out from the constraints pass through the five questions to yield options. The constraints table shows the work of steps 3 to 6. The register in the example shows the result of step 7.

Cost

DimensionLevelRationale
PreparationLowBring together two to five people. The schedule and the organisation chart supply the inventory when they are up to date.
ExecutionLowSixty minutes per problem according to Anderson. A complex problem takes longer.
DocumentationLowThe constraints table, the options register and the update of the RACI matrix.

Tools

A whiteboard or an online whiteboard (Miro, Mural) holds the inventory, the constraints and the options during the session. A spreadsheet keeps the constraints table and the options register after the session. The planning tool or task tracker (Jira, MS Project) gives each person's workload. The organisation's competency framework supplies the skills for step 2 when it exists. The RACI matrix records the responsibilities after the reassignment.

Sources

  • George W. Anderson, Design Thinking for Tech: Solving Problems and Realizing Value in 24 Hours, Addison-Wesley, 2023. Hour 11 "Guardrails for Thinking Creatively", section "Design Thinking in Action: Möbius Ideation", pp. 164-166: the definition, the strip analogy, the participants and duration, the seven steps and the five questions. Same chapter, section "What Not to Do: Avoid the Silly-Sounding Stuff": the warning about technique names. Hour 24, section "Schedule Management": the technique as a way to avoid waiting for resources.
  • Eric W. Weisstein, "Möbius Strip", MathWorld, Wolfram Research: the definition of the strip.

Anderson gives no output format and no worked example with numbers: the constraints table, the options register and the insurer case are our constructions.

Minimum Viable Product (MVP)
All techniques
Monte Carlo Simulation