Expressions · Minos & configurations
More than a team.
Consultancy, technical leadership, and engineering delivered as one accountable unit. The problem sets the composition; the Mino carries it into production.
Mino · three layers · one accountable unit
Five shapes. One beam.
The five configurations spell JOIST — the load-bearing beam the whole unit rests on.
The Mino model
One unit. Three layers.
A Mino is not just a team—it’s consultancy, technical leadership, and engineering delivered as one embedded unit. We start by understanding your business problem, then build the capability to solve it.
- 01
Strategic Consultancy
Product Owners, Project Managers
Understanding the business problem, setting priorities, and aligning stakeholders.
Value
Keeps engineering effort business-aligned.
- 02
Technical Leadership
Lead Dev, Lead Tester, Lead Ops
Setting architecture and quality direction, then translating strategy into executable engineering decisions.
Value
Bridges business strategy and engineering execution.
- 03
Engineering
Dev, Test, Ops, plus a flexible fourth role
Delivering features and ensuring product stability and performance end to end.
Value
Provides complete skill coverage without handoffs.
How a Mino forms
The composition follows the problem — understood first, then built — in four steps.
01
Understand the problem
Start with the business challenge, not a staffing request.
02
Design the Mino
Compose the right mix of consultancy, leadership, and engineering.
03
Embed and deliver
Integrate into your tools, rituals, and goals. Shipping starts.
04
Adapt and scale
As the problem evolves, roles shift and capacity scales.
The rules
- Must
Define a Mino as consultancy, technical leadership and engineering delivered as one embedded, accountable unit — never as “a team” or “a squad” alone.
- Must
Name all three layers, in order, when introducing the model: Strategic Consultancy, Technical Leadership, Engineering.
- Prefer
Describe how a Mino forms as four steps: understand the problem, design the Mino, embed and deliver, adapt and scale.
JOIST
Various flavors. One standard.
Each Mino’s focus is communicated through an iconic Tetris shape. The shape tells you the competency emphasis at a glance.
Start with a problem
I-Mino
Dev-heavy
Shipping a roadmap slice fast.
Problem · Ship a roadmap slice fast
Change the problem · the anchor stays put
The fixed consultancy cell and each silhouette’s orientation are a brand-book extension derived from consultancy-first doctrine. They are not specifications from the live site.
What is real
JOIST, the five J/O/I/S/T names, and their competency descriptors come from the live Software Development Teams page. I, J, and T also have sourced homepage use cases.
What remains open
O-Mino and S-Mino have no fuller scenario copy in the current corpus. Their silhouettes are shown without invented role mappings or claims.
The rules
- Must
Use the five JOIST configurations with their sourced descriptors: J-Mino (Ops enhanced), O-Mino (Balanced), I-Mino (Dev-heavy), S-Mino (Strategic Unit), T-Mino (Test-focused).
- Must not
Invent use cases or role mappings for a configuration. Only I, J and T have sourced use cases; O and S keep their descriptors alone.
- Prefer
Frame JOIST as the load-bearing beam the unit rests on only as a gloss, never as a sourced claim.
Extension
The anchor law
Consultancy starts first.
“Every Mino starts with consultancy, not code.”
The fixed consultancy cell and each silhouette’s orientation are a brand-book extension derived from consultancy-first doctrine. They are not specifications from the live site.
The rules
- Must
Start every Mino with consultancy: in copy, in process and in diagrams.
- Prefer
In Mino diagrams, keep the consultancy cell fixed and orange while the rest of the silhouette changes. Do not present cell coordinates or orientations as a specification.
Extension