Checking What Was Promised Before You Build It
How to verify what the CMO actually agreed to before you start building, so you don't waste time on the wrong thing.
The Problem#
You get a task: "Build the landing page for Acme's Q2 campaign." You start designing. Three days later the CMO says, "Actually, Sarah wanted a single-page scroll, not a multi-page site. We discussed it last Tuesday."
This happens because decisions live in meeting conversations that you weren't part of. Coppermind captures those decisions. Check them before you start.
Search for Decisions#
Decisions are stored as memories with type decision. Search for them directly:
search memories about landing page decisions for AcmeOr broader:
search memories about Q2 campaign decisionsDecision memories include what was agreed, who agreed to it, and when. They decay slowly (0.3/year), so even decisions from months ago still surface.
Check Commitments and Timelines#
The CMO may have committed to specific deliverables or timelines. These are stored as commitment type memories:
search memories about commitments for AcmeThis surfaces things like:
- "Ben committed to delivering mockups by March 15"
- "Sarah wants the landing page live before the trade show on April 20"
- "Agreed to deliver weekly content - 2 blog posts and 3 social posts"
If a commitment has a deadline attached, you know the real timeline - not the aspirational one.
Check Rock Status#
Larger initiatives are tracked as rocks (quarterly goals). If your task is part of a rock, check its status:
get rocks for AcmeThis shows all active rocks with their status, owner, and description. If the rock says "Website Redesign - On Track" and the description mentions specific pages, that's your scope. Don't add pages that aren't in the rock without checking first.
Check Sprint Assignments#
If the team runs sprints, check the current sprint for your deliverables:
get current sprint for AcmeThis shows sprint deliverables, who owns them, and their status. Your task might already be defined with specific acceptance criteria.
Flag Conflicts Early#
Sometimes what was promised doesn't match what's feasible. You find the commitment says "landing page live by Friday" but you know the design hasn't been approved yet. Flag it immediately:
quick note: Conflict - landing page committed for Friday but design not yet approved. Flagging to CMO.Then tell the CMO directly. The worst outcome is discovering the conflict on Thursday night.
Common conflicts to watch for:
| Conflict Type | Example |
|---|---|
| Timeline vs. scope | "5-page site by Friday" when you've never seen the content |
| Promise vs. reality | "We'll A/B test it" but no testing tool is set up |
| Conflicting decisions | Meeting 1 said "blue theme," meeting 2 said "green theme" |
| Missing prerequisites | Landing page promised but copy hasn't been written |
The 2-Minute Pre-Work Check#
Before starting any client deliverable:
switch to [client]if you haven't alreadysearch memories about [deliverable] decisions- what was agreedsearch memories about [deliverable] commitments- what was promised and whenget rocks- is this part of a larger initiative with defined scopeget current sprint- is this already in the sprint with acceptance criteria
If everything lines up, build it. If something conflicts, flag it before you start. Two minutes of checking saves days of rework.
What to Do With What You Find#
| Situation | Action |
|---|---|
| Clear decision exists | Follow it exactly |
| Multiple conflicting decisions | Ask the CMO which one is current |
| No decisions found | Ask the CMO for direction before starting |
| Decision exists but seems outdated | Verify it's still valid before building |
| Commitment deadline is impossible | Flag it immediately with a realistic estimate |
Related Guides#
Ready to try this yourself?
Coppermind is free to start and runs inside Claude. Your first meeting prep will convince you.
Try Coppermind Free