Six say represents a flexible prompt framework that helps teams align on goals, roles, and expectations before starting any project. By clearly stating who, what, where, when, why, and how, it reduces ambiguity and keeps discussions focused.
Organizations use six say to streamline communication, surface risks early, and ensure that decisions are traceable to stated objectives. The approach scales from individual tasks to cross-functional programs.
| Dimension | Definition | Owner | Success Indicator |
|---|---|---|---|
| Who | Roles and decision makers involved | Product Owner | Clear authority documented |
| What | Scope, deliverables, and acceptance criteria | Business Analyst | Signed off requirements |
| Where | Physical or digital environment, tools, and constraints | Infrastructure Lead | Environment readiness verified |
| When | Timeline, milestones, and deadlines | Project Manager | On‑schedule delivery |
| Why | Business outcomes, user value, and strategic rationale | Executive Sponsor | Measured value realization |
| How | Methodology, standards, and quality gates | Engineering Manager | Consistent process adherence |
Clarifying Context with Six Say
Applying six say at the start of an initiative creates shared context for everyone involved. Teams define constraints, assumptions, and success metrics up front, which reduces rework later.
Mapping Objectives to Deliverables
Each dimension of six say links strategic objectives to tangible deliverables. This mapping helps stakeholders understand how daily tasks connect to larger goals.
Executing Projects with Six Say
During execution, six say guides prioritization and trade‑off discussions. Product Owners refer to the documented Who, What, and Why when evaluating new requests or scope changes.
Risk Management and Communication
The Where and When dimensions highlight dependencies, resource constraints, and timing risks. Teams use this information to build buffer, coordinate handoffs, and set realistic expectations.
Governance and Continuous Improvement
Six say supports lightweight governance by making decisions and assumptions visible. Review loops compare intended outcomes with actual results, enabling data driven adjustments.
Scaling Across Programs
In larger environments, six say provides a common language across teams. Standardized prompts help leadership compare initiatives and allocate budgets more objectively.
Adoption Best Practices
- Introduce six say in kickoff meetings to build shared understanding
- Store the six say document in a centralized workspace for easy reference
- Link each decision back to the relevant dimension for traceability
- Use the dimensions as checkpoints during retrospectives
- Tailor prompts to your industry without removing core intent
FAQ
Reader questions
How does six say differ from a standard brief?
Six say adds explicit dimensions for method and environment, turning a high level brief into an actionable plan with clear quality standards and constraints.
Can six say be used for non technical work such as marketing or HR?
Yes, the structure applies to any initiative by reframing Who, What, Where, When, Why, and How to fit campaign goals, policy changes, or talent programs.
What happens if the owner of the How dimension is unavailable?
Teams should appoint a proxy, document the intended standards, and schedule a review session to validate that outputs meet quality and compliance requirements.
How often should teams revisit the six say dimensions during a long project?
Review the dimensions at major milestones, when scope changes, or when new risks emerge to ensure alignment remains accurate and decisions stay traceable.