The Fourward Method

Why "Fourward" ?

Naming is hard ... if you know me ... you'd know that I like a good play on word . Fourward is a play on forward , the idea that you move your architecture forward four layers at a time . Not one thing in isolation , not everything at once , but four . A number small enough to hold in your head , large enough to cover the landscape .

The constraint is the method . By forcing every assessment into a 4×4 structure , you avoid the two failure modes of architecture planning : doing too little (a single layer , a single concern) or drowning in a spreadsheet of hundreds of line items that nobody reads .

Besides , none of the existing industry standards allow to navigate around the full picture , some are about visualising the architecture only , others are about managing work , and none are easy to compose .

The 4×4 Principle

At the heart of the method is a matrix : 4 layers across 4 dimensions .

The default four layers

The method ships with four layers that cover a typical technology stack :

These layers are a starting point , not a prescription . Every business has a different architecture . A hardware company might replace "Clients" with "Firmware & Embedded" . A data-heavy organisation might split "Data" into "Storage" and "Pipelines" . A platform team might use "Developer Experience" instead of "Edge" . The method works regardless of what the four layers are , as long as there are exactly four and they are collectively exhaustive for your landscape .

The four dimensions

Every layer is assessed through four lenses . These are the questions you hold up to each slice of your architecture .

The rating scale

Every facet receives a rating on a four-point scale . The scale is intentionally coarse . Fine-grained scores (7 out of 10 vs 6 out of 10) create a false sense of precision . Four levels are enough to drive the right conversations and the right actions .

Every intersection of a layer and a dimension is a facet . Each facet gets a current rating and a target rating . The gap between them is where the work lives .

Example landscape matrix . Each row is a layer , each column a dimension . The badges show current and target ratings .

Why four ?

Four is a cognitive sweet spot . Research on working memory suggests people can comfortably hold about four items in focus at once . The method exploits this :

• Four layers means you can see the full stack without scrolling .
• Four dimensions means you assess from enough angles to catch blind spots , but not so many that the assessment becomes a chore .
• Sixteen facets (4×4) is a landscape you can absorb in a single view .

Four also maps naturally to quarters . A year has four , and each quarter becomes a natural checkpoint for re-assessment . You can align gap activities to quarterly planning cycles , focus one quarter per layer , or rotate dimensions across the year . The number four isn't just a cognitive constraint , it's a planning rhythm .

The constraint also enforces MECE thinking , mutually exclusive , collectively exhaustive . When you only have four slots , you're forced to group things meaningfully . You can't have a catch-all "other" bucket when the limit is four .

Recursive Decomposition

The 4×4 structure doesn't just apply at the top level . Any layer can be decomposed into exactly 4 sub-layers , and each of those sub-layers can be decomposed further . The structure is fractal .

Edge & Networking
├── CDN & WAF
├── DNS & Domains
├── Load Balancing
└── API Gateway
    ├── Rate Limiting
    ├── Auth & Routing
    ├── Transformation
    └── Observability

At every level of depth , the same 4×4 matrix applies . The same four dimensions . The same rating system . This means :

• Zoom out to see the health of the entire landscape in 16 facets .
• Zoom in to see the health of a specific sub-system in 16 facets .
• Compare across depths using the same vocabulary and scale .

The recursion is opt-in . You only decompose a layer when you need more detail . A layer rated "Strong" across all dimensions probably doesn't need sub-layers . A layer rated "Critical" on two dimensions probably does , you need to know where in that layer the problems live .

The rule of four

Every decomposition must produce exactly four children . Not three . Not five . This constraint forces clarity :

• If you can only think of three , you're missing something , look harder .
• If you have five or more , two of them probably belong together , merge them .
• The exercise of fitting things into four slots is itself valuable . It surfaces assumptions and reveals boundaries you hadn't articulated .

The Assessment Loop

The method follows a repeating cycle :

Reading the Landscape

The 4×4 matrix is designed to be read at a glance . Here's what to look for :

Patterns across layers

If a single layer is critical or weak across multiple dimensions , that layer needs dedicated investment . It's not just an automation problem or a risk problem , the layer itself is underdeveloped .

Patterns across dimensions

If a single dimension is weak or critical across multiple layers , you have a systemic issue . For example , if "Automation" is weak everywhere , the problem isn't in any one layer , it's a gap in engineering culture or tooling .

The gap count

The total number of gap activities , and their priority distribution , tells you about overall landscape health :

• Many P0s , the architecture is in crisis , focus on stabilisation .
• Mostly P1s , healthy backlog , functional but needs planned investment .
• Mostly P2s , good shape , improvements are incremental .

Build , Iterate , KTLO , Retire

The Fourward Method assumes a lifecycle for every layer :

The lifecycle is a loop , not a line . Layers don't stay in KTLO forever . Technology evolves , requirements change , and what was "Strong" two years ago may be "Adequate" or "Weak" today . The assessment loop catches this drift . Sometimes that means cycling back to Iterate . Sometimes it means moving to Retire and replacing the layer entirely . Either way , the method surfaces the signal before the decay becomes a crisis .

Principles

1. Constraint enables clarity . Four is not arbitrary , it's a forcing function . The method works because of the limit , not despite it .
2. Assess before you act . The matrix exists to make the current state visible . Resist the urge to jump to solutions before you've mapped the landscape .
3. Gaps are normal . A matrix full of "Strong" ratings is either dishonest or means you're over-investing . Gaps are healthy , they tell you where to focus .
4. Depth is earned . Don't decompose a layer into sub-layers until you need to . Start coarse , go deeper where the problems are .
5. The matrix is a conversation tool . The most valuable output isn't the matrix itself , it's the conversations it provokes . When engineers , managers , and leadership look at the same 4×4 grid , they can align on priorities without a 50-page document .
6. Forward , four at a time . Don't try to fix everything . Pick the highest-priority gaps , execute , re-assess . Progress is iterative .