Baseline assumptions
To get started documenting Pentacle, let’s get some baseline assumptions out of the way.
- We define each prong in terms of its outcomes, especially which one of these outcomes we might judge to be the most crucial.
- For the sake of moving the discussion on quickly without “or’s” and ”/‘s” (say that out loud), we call everything “product” - namely product, project, service, venture, etc.
The pentagonal
- Brainstorm
- Map
- Wireflow
- Prototype
- Engineer
Brainstorm
Definition
Brainstorm is a coordinated set of activities toward establishing a product charter.
A product charter is a single source of truth of the product, defining its goals and boundaries. While some parts of charter may be updated as the product progresses, most of it, especially its goals should ideally be almost carved in stone. This way, the product team doesn’t stray.
Any change to the product’s goals might actually mean a new direction, that is, a new product, entirely. Any such drastic changes to the charter must be carefully weighed.
A successful product is a testament to a successful charter, a successful Brainstorm.
Outcomes
- Possible solutions to build
- High-level concept of product,
- Creative brief
- User personas
- Empathy maps, and
- Product Charter
Actions
Map
Wireflow
Prototype
Engineer
References
- The Graphic Design Process, Baseline Education Ltd. Accessed Apr. 8, 2024
- Product charter: What’s included and how to create one (with examples), Bart Krawczyk, Log Rocket. Accessed Apr. 10, 2024.
- 3 elements every project charter needs, Julia Martins, Asana.com. Accessed Apr. 10, 2024.