Prodigent

Design Against Organisational Knowledge

The best input to a design discussion is what your organisation already knows about the systems you are about to change.

Strong engineers do not design in a vacuum. They ask what is already true. In large organisations, answering that question can take longer than proposing the design itself.

Before you propose options

  1. 1

    Gather system context

    What do these services do, what depends on them, and what is fragile?

  2. 2

    Pull known constraints

    Compliance, capacity, team ownership, and historical landmines.

  3. 3

    Review related decisions

    What did the organisation already choose, and why?

  4. 4

    Identify people with expertise

    Who will catch the assumptions your diagram cannot see?

Bring organisational knowledge into design

Prodigent surfaces relevant systems, decisions, risks, and people while engineers reason about a change.

Try Prodigent free