GOST Participant Enablement — Consultant Methodology

How the consultant identifies the need, gathers inputs, and positions this tool with the client. This file is for the human consultant, not the agent.

Where This Fits in the Engagement

The GOST Participant Enablement Kit is triggered after GOST training has been delivered and before tactic submission deadlines. It fills the gap between "participants were trained" and "participants actually submit their plans."

This is a change management tool, not a training tool. It does not teach GOST. It removes the friction between understanding GOST and doing the work.

Typical trigger point in the engagement timeline:

GOST Training Delivered → Tactic Submission Deadline Approaching → Submissions Not Coming In → This Kit

Recognizing the Need

Signals That This Kit Should Be Deployed

• Low submission rate — deadline has passed or is approaching and fewer than 50% of participants have submitted
• Pushback on the form — participants complain the form is "too much work" or "confusing"
• Passive leader problem — the internal client-side leader responsible for driving accountability is not doing so (won't convene working sessions, won't follow up, passes pushback along instead of addressing it)
• Training-to-action gap — participants understood the material in training but freeze when they sit down alone to produce the output
• Consultant bottleneck — the consultant is being asked to hand-hold individual participants through the form, which doesn't scale
• Format resistance — participants are submitting in wrong formats or asking "can I just send an email?" (they want to do the work but the form is the barrier)

Signals That This Kit Is NOT the Right Intervention

• Participants don't know what GOST is — the problem is training, not enablement. Train first.
• No goal or objectives exist — GOST framework isn't set up. Build the framework first.
• The resistance is political, not practical — participants are refusing as a power move or organizational protest. This requires a leadership conversation, not a tool.
• One or two participants struggling — if it's 1-2 people, a coaching conversation is faster than deploying a kit. This tool is for when the problem is systemic.

Gathering the Inputs

Before You Ask the Client for Anything

Review what you already have from the engagement:

1. GOST training materials — do you have the deck, facilitator guide, and tools? These contain the goal, objectives, and template.
2. Session transcripts — has the participant resistance been discussed in sessions? What did the client say about it?
3. Client reference data — company name, department names, leader names, tool names.

Most of the required inputs should already be in your files. Run the Required Inputs checklist in 01-gost-enablement-context.md against what you have before asking the client for anything.

What You May Need From the Client

What You Do NOT Need From the Client

• Individual department strategies — the prompt asks participants to provide their own
• A completed golden example — the kit includes a default HR example that works across industries
• Permission to use AI tools — the prompt works with whatever tool the participant already has access to (Copilot is built into Office; most people have at least that)

Positioning the Tool With the Client

The Conversation

This tool works best when the consultant positions it as making their life easier, not as a workaround for participant failure.

Frame: "I put together something that makes the tactics planning process as easy as having a conversation. Your team pastes a prompt into their AI tool, answers some questions, and gets a completed planner they can email you. Takes about 15 minutes."

Do not frame it as:

• "Your team is struggling, so I built a crutch" — this shames the participants
• "This replaces the training" — it doesn't, and saying so undermines the training investment
• "This will solve the problem" — it removes friction, but the consultant still needs to review submissions and the client-side leader still needs to set expectations

Handling Client Reactions

"Will the AI do the thinking for them?" "It guides the thinking — it asks questions and pushes back on vague answers. But they have to provide the substance: what they're working on, what success looks like, who they need things from. The AI can't answer those questions for them."

"I don't want them using AI for this." Probe: is the concern about quality, authenticity, or security? If quality — the prompt enforces SMART criteria more rigorously than most people would on their own. If authenticity — the participant still has to answer the questions; the AI structures their thinking. If security — the prompt contains only the company goal and objectives (which are on the training deck everyone already has). Participant data stays in their own AI session.

"Can't we just make a simpler form?" "That's what we tried. The form isn't the problem — the thinking is the problem. People freeze when they look at a blank form. This tool turns the blank form into a conversation."

"Our team doesn't use AI." "Most of them have Copilot built into their Office suite already. If not, ChatGPT is free. The instructions walk them through it step by step — no AI experience needed."

After Deployment

What to Watch For

• Submission quality — are the tactics actually SMART? Are KPIs real numbers? Are backward plans realistic? The prompt enforces this, but participants can still rush through.
• Copy-paste output — some participants will submit the AI's output verbatim without reviewing it. This is fine for a first submission but the consultant should flag anything that looks un-reviewed in the quality check.
• "It didn't work" reports — usually means the participant's LLM truncated the prompt (too long for free-tier context windows) or they pasted only part of it. Solution: have them try a different tool or check that they copied the complete prompt.
• Participants who still don't submit — this tool removes friction for people who want to do it but are stuck. It does not solve for people who are actively resisting the process. Those are separate conversations.

Feeding Back Into the Engagement

Every deployment of this kit produces constraint evidence:

• If it works (submissions come in, quality is acceptable) — the constraint was friction/scaffolding, not resistance. Note this in the CPM as a resolved or reduced constraint.
• If submissions come in but quality is low — the constraint may be deeper: participants don't understand their department strategy, or the strategies themselves are weak. Route back to the Strategy Card work.
• If participants still don't submit — the constraint is behavioral or political, not practical. This is CPM evidence for a leadership accountability constraint.
• If the client-side leader uses the tool as a reason not to follow up (the "passive leader" pattern) — "I sent them the tool, what more can I do?" — the constraint is leadership sponsorship. Route to change management / ADKAR work.

Connection to Other Kit Work