Stakeholder Persona: Lead Developer

Field Value
Category INTERNAL Stakeholder
Actor Type human
Primary Goal Translate architecture and governance intent into practical implementation behavior.
Persona ID aud-lead-developer
Created / Updated 2026-02-28
Domain / Context Spec Kitty architecture 2.x
Status canonical

Overview

  • Role Focus: Delivery execution, code quality, and doctrine adoption.
  • Primary Function: Curates practices, validates feasibility, and applies governance decisions in implementation workflows.
  • Environment / Context: Active feature streams with frequent branch-level iterations.

Core Motivations

  • Professional Drivers: Faster implementation with fewer ambiguous handoffs.
  • Emotional or Cognitive Drivers: Wants high signal in docs and low process overhead.
  • Systemic Positioning: Bridge between architecture intent and daily coding operations.

Desiderata

Category Expectation / Need Description
Information Actionable guidance Expects architecture docs to clarify behavior, not restate code structure.
Interaction Fast feedback loops Needs rapid validation for governance and workflow changes.
Support Reusable patterns Prefers patterns that can be applied across features without re-interpretation.
Governance Explicit activation rules Must know when a curated practice is actually active.
Decision Authority Practice adoption recommendation Proposes and validates practical adoption paths before final approval.

Frustrations and Constraints

  • Pain Points: Policies that are unclear, duplicated, or disconnected from runtime commands.
  • Trade-Off Awareness: Accepts stronger process if it clearly reduces rework.
  • Environmental Constraints: Release timelines, mixed agent capabilities, and incomplete prior context.

Behavioral Cues

Situation Typical Behavior Interpretation
Stable / Routine Optimizes command workflows Improves throughput through repeatable sequences.
Change / Uncertainty Requests concrete examples Uses examples to assess implementation realism.
Under Pressure Focuses on deterministic minimum viable path Prioritizes reliable completion over ideal abstractions.

Collaboration Preferences

  • Decision Style: Pragmatic and evidence-based.
  • Communication Style: Direct, implementation-oriented, and concise.
  • Feedback Expectations: Specific blockers, concrete alternatives, and clear acceptance criteria.

Design Impact

  • Affected By: Doctrine curation flow, charter activation path, and validation gates.
  • Needs From Design: Clear ownership of transitions from proposal to active behavior.
  • Risk If Ignored: Shadow conventions and inconsistent implementation quality.
  • Acceptance Signal: Curated practices can be activated and observed without manual interpretation.

Measures of Success

Dimension Indicator Type
Performance Time from curated proposal to active practice Quantitative
Quality Defect/rework rate after governance change adoption Quantitative
Growth Team reuse of curated doctrine patterns Qualitative

Narrative Summary

The Lead Developer operates where architecture decisions meet daily delivery. They need governance artifacts to be operationally useful and executable through commands, not just aspirational prose. Their trust increases when each policy change has a clear activation and validation path.

Edit this page