An imagined planning example, not an account of a client project or a description of every hālau.
This is an illustrative design exercise. Imagine a hālau preparing for a performance, with practices that change as the event approaches. It is not a report of work delivered to a client, and it does not assume that every hālau organizes its season in the same way.
Ask what the season looks like
A recurring weekly calendar may handle some of the work well. Before deciding whether anything more is needed, ask the people coordinating it to walk through a season. What stays fixed? What changes? Which changes need someone’s approval, and who needs to know?
- The event gives the plan a reference pointIn this imagined example, the event connects practices, preparation tasks, and orders. A change can then be reviewed in the context of the larger plan.
- Relationships need their own placeAsk how families and participants should be represented. The right arrangement comes from the group’s needs, including who can see and change which details.
- An order has a pathAn order may involve a size, an approval, a supplier, and an expected arrival. Keeping those steps visible can be more useful than treating the order as a single checkbox.
Look at the work beside the official tool
A separate spreadsheet or notebook can show what people need to remember. It might reveal missing functionality, or it might simply be an effective part of the existing process. Ask what it does before assuming it needs to be replaced.
The useful question is: what are people keeping track of, and why?
A small prototype could show an event, its related work, and the questions waiting for a person. Use fictional details first. Let the people who know the process explain what is missing or misleading before connecting real information.
Choose the smallest useful change
The answer might be a better view in an existing tool, a shared checklist, or a focused custom workflow. This exercise does not establish that a custom application is necessary. It offers a way to discover what the calendar needs to describe.
The same approach can help with other seasonal work: start with the shape of the year, then inspect a typical week. Keep the people who make the decisions involved in describing both.