Mandala chart
Place a topic in the center of a nine-cell grid and explore eight related directions before choosing ideas to develop.
Use a Mandala chart when discussion keeps returning to the same idea. The center holds one topic; the surrounding cells prompt different perspectives. A direction can become the center of a separate chart for further exploration.
One clear topic and ideas from several relevant perspectives.
Eight possible directions, gaps to explore, and selected ideas for further development.
How to use it
- Write one topic in the center.
- Explore up to eight distinct directions around it.
- Use a promising direction as the topic of another chart if more detail is needed.
- Remove duplicates and choose ideas to develop or test.
Keep its limits in mind
The cells are perspectives, not a required sequence or proof of complete coverage. Leave a cell blank when you need more thought. Mandalachart is a registered trademark of Clover Management Research Institute; this is an independent practice worksheet.
Exploring ways to make client reviews easier
Fictional example: six colleagues at Yunqiao explore how to shorten waits for client reviews. Their discussion has focused mainly on reminders; the grid broadens the options.
On a small screen, scroll across the diagram to read it.
Ideas, not outcomes: The eight directions are proposals. They do not establish that registration-free access or reminders will shorten reviews.
Further exploration: The information direction suggests a change summary, a comparison view, and a checklist of items to confirm. These are three alternative ideas, not completed features.
Next step: Use a prototype to test whether a change summary helps clients understand what they need to review.
Three reasons to reset the central question
First, stop if the center contains several unrelated ambitions. “Improve the whole client relationship” can absorb pricing, delivery, support, and contracting without helping anyone decide what to explore. Choose one situation and one difficulty. A direction is relevant when you can explain how it bears on that center, rather than merely fitting the organization’s wider agenda.
Second, pause when eight cells become a completion quota. Synonyms for reminders do not provide eight perspectives. Keep duplicates visible while collecting ideas, then merge them with reasons. An empty cell is a prompt for inquiry, not proof that the team has failed. Eight filled cells also cannot prove that every important perspective has been covered.
Third, do not treat a popular direction as customer evidence or a resource commitment. Colleagues can suggest an experience without knowing whether clients need it or whether the team can deliver it. Separate the proposed benefit, the assumption behind it, and the next check. The grid supports exploration; it does not rank feasibility or authorize implementation.
Choose exploration, variation, description, or selection
The worksheet above contains one nine-cell chart. To explore a direction further, make it the center of another chart or separate note; the current page does not automatically build a complete expanded chart. Use another method when the question has moved beyond finding perspectives.
| Material and question | Method | Output and limit |
|---|---|---|
| One bounded topic needs more perspectives | Mandala chart | Distinct directions and gaps; not exhaustive coverage. |
| One existing concept needs concrete changes | Osborn’s checklist | Variations from nine prompts; not a validated solution. |
| One selected idea needs a mechanism and a test | Idea concept sheet | A discussable concept; no proof of demand. |
| Feasible candidates and explicit criteria are available | Decision matrix | Reasoned tradeoffs; scores remain judgments. |
Expand the review-wait discussion without inventing research
The complete fictional Yunqiao packet is a team of six colleagues exploring shorter waits for client reviews. Discussion has concentrated on reminders. The eight supplied proposals concern access, information, incentive, coordination, feedback, pacing, reminders, and safeguards. No client interviews, measured waiting times, implementation budget, or observed improvement are supplied. The six people are idea contributors, not six customers who validated a problem.
Write “shorten waits for client reviews” in the center, then inspect the proposals below. Some concern getting into the experience; others concern understanding or completing it. None demonstrates the cause of waiting. Registration could be a barrier for some people, while other delays may involve authority or unclear review requirements. The chart does not distinguish those explanations without further observation.
The information direction produces three supplied alternatives: a change summary, a comparison view, and a checklist of items to confirm. Preserve them separately. A summary highlights changes; a comparison shows differences; a checklist specifies the requested judgment. They might complement one another, but combining all three immediately would make a larger concept before the first uncertainty has been tested.
| Direction | Supplied proposal | Assumption to check |
|---|---|---|
| Access | Review without registering | Authorized clients can enter without weakening access controls. |
| Information | Make required checks clear | Clients do not know what needs attention. |
| Incentive | Explain the project benefit of timely feedback | The stated benefit matters to this reviewer. |
| Coordination | Name one review owner | That person has the authority and capacity to coordinate. |
| Feedback | Voice, text, and image annotations | Different input modes address a real task difficulty. |
| Pacing | Review in stages | Stages reduce burden without losing the whole decision. |
| Reminders | Base reminders on the deadline | The deadline is agreed and contact is appropriate. |
| Safeguards | Retain versions and allow withdrawal | Version and withdrawal rules can be explained and supported. |
Develop one direction and record what would change your mind
The proposed next step is a change-summary prototype, keeping the comparison view and checklist as alternatives. Ask a target reviewer to identify what changed and what response is requested using representative material. Agree the task, participation, observation procedure, and acceptance conditions before testing. None of those arrangements is already confirmed in the packet. Do not announce that a prototype has reduced waiting merely because a colleague understands the drawing.
For the proposed review, retain the original directions, why information was selected, the prototype version, the reviewer’s actual responses, and places requiring explanation. Measure task understanding separately from elapsed review time. Waiting involves the interval between a defined request and a defined response, plus incomplete cases; it is not the same as time spent reading a summary.
If clients understand the changes but still cannot approve them, investigate authority or coordination rather than polishing the summary indefinitely. If they cannot identify what needs attention, revise the information concept before expanding it. Record whether to continue, switch alternatives, or return to the central question. The case ends with a bounded investigation, not a winning direction or a completed customer trial.
Check your work
- Each direction relates to the center topic.
- The cells offer different perspectives rather than repeated wording.
- Empty cells remain visible as gaps.
- Selected ideas have a concrete next check.
Framework references
References explain the framework and its scope; they do not validate the fictional example's results.
Put the framework to work
Copy the outline and add your question, evidence, and open questions.