DSTA ProductOps Co-pilot

Prompts

Persona generator

draft a persona from research evidence

ResearchDigitalCLARA

Output: Markdown persona with Name, Summary, Goals, Pains, Context, Quote, and Evidence sections — every claim sourced.

Paste into a CLARA-enabled chat

CLARA will confirm the route, ask for anything she still needs in one batched question, and show you the draft before filing.

Use CLARA's `persona-generator` for <programme name>.

What CLARA will ask you for

  • Programme name — your programme's name (e.g. SKYPROTECT).
  • Track — the slice of the programme this artefact belongs to (workstream, capability area, feature line, etc.), or Programme-wide if it spans tracks.
  • Persona name — short identifier for the persona (e.g. "Field operator", "Watch officer").
  • Inputs — CLARA will search the programme's Confluence space for interview transcripts, observation notes, or survey responses; themes and friction points from the research synthesis (optional). You can also paste fresh material if it's not in Confluence yet.

Where the output lands

Knowledge Base/{{track}}/Personas/{{persona-name}} inside your programme's Confluence space.

Tips

  • Don't ask for multiple personas in one go. Generate one at a time and let each one earn its place.
  • The "non-obvious trait" check matters because personas blur into one another when every persona is a "busy professional who values efficiency." The differentiating trait is what makes the persona useful in design discussions.
  • The persona output feeds directly into the journey-map drafter, service-blueprint drafter, and PRD generator.

Where this fits in the chain

Use after

These prompts produce outputs you can paste as inputs here.

Research synthesiser

turn interview transcripts and field observations into a single Research synthesis page covering themes, friction, problem statement, and success criteria

Feeds into

The output of this prompt is consumed by these downstream prompts.

Journey-map drafter

draft a current-state journey map for a persona

PRD generator

draft a v0 PRD from the problem-impact ranking, research synthesis, and prior framing

Problem-impact ranker

consolidate the captured problems for a programme into a single ranked Problem-impact analysis — each problem scored on reach, severity, evidence and leverage, grouped into leverage tiers, so the team knows which problem to build for first

Service-blueprint drafter

draft a service blueprint linking user actions to front-stage and back-stage support