Command Center Prototype

Design Map Workbench

A first draft of the one-row-at-a-time journey map, connected to saved DesignID, DesignPD, and Spiritual Gifts signals.

Profile layers3/3DesignID, DesignPD, and Spiritual Gifts detected for this prototype view.
Prototype scope:Draft entries are saved in this browser only. The next step, after the workflow feels right, is a real database-backed Design Map record per participant, group, or organization.Back to Command Center

Row-by-row builder

Behavior Line

Name visible behavior. Keep it concrete enough that someone else could watch it happen.

0 of 48
01

Define

What is the topic, calling, burden, opportunity, or decision?

02

People

Who is affected, needed, missing, or already carrying part of it?

03

Clarify

What must be understood, measured, named, or discerned?

04

Prepare

What plan, structure, tool, money, or permission has to exist?

05

Test

What small test, experiment, conversation, or prototype proves the path?

06

Launch

What gets launched, reviewed, handed off, repeated, or completed?

Slow-run check

Likely friction points to solve next

People may confuse rows with phases.

The row tabs stay fixed while phases repeat, so the user always knows whether they are mapping behavior, people, process, needs, gaps, alignment, or commitment.

Suggestions can become too generic.

This draft uses profile-aware chips. The next version should pull from the full DesignID Journey Mapping sheet and filter by project type.

Groups need agreement, not just notes.

Corporate and ministry versions should add voting, confidence, owner assignment, and disagreement markers before the final commit row.