Assign positions to your team members. WISER uses positions (not job titles) to distribute responsibility across six roles.

WISER Positions

• Sponsor: Executive authority. Owns the business case, removes organizational blockers, makes final calls.
• Architect: System designer. Maps current state, designs solutions, manages technical complexity.
• Sage: Domain expert. Brings deep process knowledge, validates assumptions, catches blind spots.
• Scout: Field researcher. Observes real work, talks to frontline people, tests in the wild.
• Smith: Builder. Creates prototypes, configures tools, makes things work.
• Keeper: Playbook steward. Maintains documentation, tracks decisions, ensures nothing gets lost.

<aside> 💡 One person can hold multiple positions. A three-person team might double up. The key is that every position is explicitly assigned; not assumed.

</aside>

Team Roster

Objective: Track who fills each Position and their availability so no accountability is orphaned.

When to use: At project kickoff and whenever team composition changes.

Inputs: Team member names, their job titles, Position assignments from team setup discussion.

Position: Architect maintains. Sponsor approves assignments.

<aside> 💡 One person can hold multiple Positions. The key is that every Position has exactly one owner, not zero, not two.

</aside>

Team Roster