Skip to content
Software Behaviorby Joost van der Zwan
Index

Framework · Sequence · from Introduction

Role Friction Map

A diagnostic for testing whether friction comes from role scope, environment, capability, or the evidence available.
Read the chapter

The framework

Fig. · Role Friction Map
  1. What am I hired to do?: Name the official shape of your role: what is assigned, rewarded, and expected.
  2. What am I capable of seeing?: Name the product questions you notice, even when they are not formally yours.
  3. What do I keep wanting to influence?: Name the decisions you cannot stop caring about and the direction your work is pulling you.
  4. What am I not invited to touch yet?: Name where you have opinions but no authority, or where you are brought in too late.
  5. Where do I feel most alive in the work?: Name the moments where your attention sharpens, then test whether the pattern survives changes in workload, environment, and responsibility.
  1. 01

    What am I hired to do?

    Name the official shape of your role: what is assigned, rewarded, and expected.

  2. 02

    What am I capable of seeing?

    Name the product questions you notice, even when they are not formally yours.

  3. 03

    What do I keep wanting to influence?

    Name the decisions you cannot stop caring about and the direction your work is pulling you.

  4. 04

    What am I not invited to touch yet?

    Name where you have opinions but no authority, or where you are brought in too late.

  5. 05

    Where do I feel most alive in the work?

    Name the moments where your attention sharpens, then test whether the pattern survives changes in workload, environment, and responsibility.

4 · Do

How to use it

Write a short answer next to each line, then compare attention with fatigue, context, demonstrated capability, and evidence. The output is a diagnosis to test, not proof that a role has been outgrown.

5 · Save

The Product Architect · Role Friction Map

Framework · Sequence