Concept — illustrative interface
Tanda.
A clearer view of
what happens next.
A calmer operations workspace. An exploration of shared priorities, clear ownership and considered handovers for a fictional business.
WEEKLY PLAN / SAMPLE WEEK
The week, in focus.
Shared priorities. Clear ownership.
- OP-014
Workshop materials
Confirm the materials listOwnerOperationsIn preparationDue Tuesday - OP-015
Supplier review
Compare delivery termsOwnerProcurementReviewDue Wednesday - OP-016
Delivery handover
Prepare the packing notesOwnerLogisticsPlannedDue Friday
Procurement → OperationsDelivery terms need confirmation before the materials request moves forward.
Illustrative content / Weekly plan view
The starting point
The work between the work.
Imagine a small workshop coordinating materials, supplier decisions and delivery preparation. A request can travel between several roles before it is ready to move on. Tanda asks how a shared workspace could make that next step explicit, without adding another layer of administration.
The intended workflow
One workflow. Different responsibilities.
The intended users are an operations coordinator planning the week, a procurement lead checking dependencies, and a delivery coordinator preparing the handover. These roles are a design scenario, not the result of customer research.
- 01
Plan
Give a request a name, an owner and a next step before it enters the weekly plan.
- 02
Review
Bring an outstanding decision and its dependency into the same view as the work it affects.
- 03
Hand over
Pass along a clear preparation note, so the receiving role can see what still needs attention.
Design decisions
Clarity before more features.
The interface prioritises the task, the accountable role and the next decision. Visual hierarchy does the organising; it does not depend on decorative charts or invented performance indicators.
A useful weekly rhythm
A shared weekly plan makes related work easy to scan. Specific task names are more helpful here than aggregate activity counts.
Status with meaning
Review, Planned and In preparation are written out. A restrained ember rule draws attention to a dependency without making colour the only signal.
Context at the handover
A separate handover view brings the reason, required information and receiving role together instead of hiding them in a busy overview.
A closer look
The next decision, with its context.
HANDOVER BRIEF / OP-015
Supplier review
A decision with enough context to move forward.
- Responsible role
- Procurement
- Receiving role
- Operations
- Stage
- Review
- Due
- Wednesday
PREPARATION NOTES
- Compare the options
Review the sample supplier notes against the materials list.
- Record the decision
Include the preferred option and the reason for choosing it.
- Brief operations
Pass on the agreed delivery window before preparation begins.
Delivery terms need confirmation before the materials request moves forward.
Illustrative content / Handover brief view
Accessibility & mobile
A smaller screen, not smaller thinking.
The coded preview reflows around its own available width. On a phone, task rows become labeled stacks and the handover note follows the plan in reading order. Nothing essential sits outside the viewport.
Readable by structure
Semantic lists and description lists preserve relationships between tasks, roles and status. Visible text repeats every colour-coded meaning.
Calm by default
There is no animation or hover-dependent information in the concept surface. The surrounding site supports reduced motion and visible keyboard focus.
Interaction still to design
The previews have no controls. A functional product would need tested keyboard patterns, form errors, loading states and assistive-technology validation.
The boundary of this study
What exists. What comes next.
Implemented in this study
Original server-rendered HTML/CSS views of the weekly plan and handover brief, using shared fictional data. Container-based responsive layouts, text status labels and semantic content are implemented. The portfolio pages and their navigation work.
Proposed, not implemented
Task creation, editing, search, filters, approvals, notifications, persistence, accounts and integrations. There is no live operational data or connected business system. No usability research or business outcomes are claimed.
A relevant next step
From a direction to a useful product.
The next step would be to validate the workflow with the people doing the work, agree on a focused first release, and prototype the highest-risk interactions before building a connected system.