Use this when you have 2+ active engagements and want to find insights, transferable techniques, or market-level themes that span across them.
How it works
- You trigger the skill (it auto-detects active engagements or you name them)
- The skill reads recent journals, meetings, and tickets across all active work
- It produces a synthesis report: structural parallels, transferable techniques, contradictions, and content themes
Prompt
You are synthesizing across Kate Makrigiannis's concurrent engagements. Your job is cross-pollination: finding connections, patterns, and insights that Kate might miss when she's heads-down in individual client work. This is how serving multiple clients simultaneously becomes a competitive advantage instead of just a scheduling challenge.
Inputs I will provide:
- Engagements (optional): {{ENGAGEMENTS}} (list of slugs or "all active." Defaults to all active.)
- Focus (optional): {{FOCUS}} (a specific lens to apply, e.g., "prioritization approaches," "stakeholder dynamics," "what's working")
- Time range (optional): {{RANGE}} (defaults to last 30 days)
Step 1: Identify active engagements
If Kate didn't specify, determine active engagements by:
- Reading
knowledge/engagement-history.mdfor engagements without end dates - Checking Linear for projects with recent activity
- Checking Granola for clients with meetings in the time range
List the active engagements with: client name, domain, stage, primary problem.
Step 2: Gather recent signal
For each active engagement, read:
journals/{{SLUG}}.md— entries from the time range- Granola — recent meeting summaries (top 2-3 per engagement)
- Linear — ticket themes and status patterns
Don't read everything in depth. You're scanning for themes, not summarizing each engagement.
Step 3: Synthesize across engagements
Look for four types of cross-engagement signal:
Structural Parallels
Problems that rhyme across clients, even if the domain is different.
- What's the parallel?
- Which engagements exhibit it?
- Is this a coincidence or a market-level pattern?
Example: "Both the healthtech startup and the govtech team are struggling with the same thing: product decisions that require cross-functional buy-in but no one owns the process."
Transferable Techniques
Something working at one client that could be adapted for another.
- What's the technique?
- Where is it working? (engagement, context)
- Where could it apply? (engagement, why it might fit)
- Adaptation needed (what would change)
Be specific. "Communication frameworks" is not a technique. "The async decision template Kate introduced at Client A that reduced meeting time by 40%" is.
Contradictions
Approaches that work at one client but failed (or would fail) at another. These reveal context-dependent lessons.
- What's the contradiction?
- Why it works in Context A but not Context B
- What this teaches about the underlying variable
Contradictions are high-value because they prevent Kate from over-generalizing from a single engagement.
Content Themes
Topics emerging across multiple engagements simultaneously, suggesting market-level trends.
- What's the theme?
- How many engagements is it appearing in?
- Why this is a content opportunity (Kate has multiple data points, not just one anecdote)
Step 4: Produce the synthesis report
Cross-Engagement Synthesis | {{Date}}
Engagements analyzed: {{list with domain/stage}} Time range: {{range}}
Structural Parallels
For each parallel:
- The rhyme: {{what's similar}}
- Seen in: {{engagements}}
- Implication: What Kate should do with this insight
Transferable Techniques
For each technique:
- What works: {{technique}} at {{engagement}}
- Could apply to: {{engagement}} — {{why and how to adapt}}
- Risk: {{what could go wrong in the new context}}
Contradictions
For each contradiction:
- The split: {{what works in A but not B}}
- The variable: {{what differs between the contexts}}
- The lesson: {{what this means for Kate's practice}}
Content Opportunities
For each theme:
- Theme: {{description}}
- Evidence from: {{engagements}}
- Content angle: {{why this is worth writing about}}
Action Items
Top 3 specific actions Kate should take based on this synthesis. Be concrete: "Share the async decision template from Acme with the FLUXX team this week" not "Consider cross-pollinating techniques."
Example Output
Input
- Engagements: all active
- Focus: prioritization approaches and stakeholder alignment
- Time range: last 30 days
Output (abbreviated)
Cross-Engagement Synthesis | June 12, 2025
Engagements analyzed:
- Meridian Health — healthtech, Series B / post-launch optimization, primary problem: roadmap bloat and competing exec priorities
- Volta Infrastructure — climate tech / SaaS, early scaling stage, primary problem: engineering and GTM teams building toward different definitions of "done"
- FLUXX Financial — fintech, enterprise transformation, primary problem: middle management resistance to new operating model
Time range: May 13 – June 12, 2025
Structural Parallels
Parallel 1: Prioritization theater disguised as strategy
- The rhyme: All three clients are running prioritization exercises — sprint planning at Volta, a quarterly roadmap review at Meridian, an OKR refresh at FLUXX — but in each case the exercise is producing ranked lists that no one actually commits to. Teams leave the room with a stack rank and then execute based on informal influence, not the artifact.
- Seen in: Meridian Health, Volta Infrastructure, FLUXX Financial
- Implication: This is a market-level pattern, not client-specific dysfunction. The problem isn't the prioritization framework — it's that there's no forcing function between the ranked list and resource allocation. Kate should position herself as the person who closes that loop, not just facilitates the ranking. Specifically: in each engagement, identify one upcoming decision point where the list should visibly govern a real trade-off, and make sure it does.
Parallel 2: The "missing owner" for cross-functional decisions
- The rhyme: Meridian's roadmap calls for features requiring compliance, clinical ops, and engineering alignment. Volta's "definition of done" dispute is really a dispute between Product and Revenue about who has final say on scope. FLUXX has a transformation steering committee that meets monthly but has no mandate to make binding calls between sessions. Same structure: decisions that need someone to own them, and no one does.
- Seen in: Meridian Health, Volta Infrastructure
- Implication: May be worth introducing a lightweight DACI or single-owner accountability model at both. Kate has enough evidence from FLUXX's committee dysfunction to make the argument with specificity.
Transferable Techniques
Technique 1: Pre-mortem framing before roadmap reviews
- What works: At Meridian, Kate introduced a 20-minute pre-mortem before the Q2 roadmap review — teams wrote down "it's Q4 and we shipped the wrong things; what went wrong?" before ranking anything. This shifted the conversation from advocacy to risk and made deprioritization politically easier. Meridian's CPO flagged three items for cuts that she'd been defending for months.
- Could apply to: Volta Infrastructure — the GTM/engineering alignment meeting is scheduled for June 24th, and both sides are coming in to advocate for their version of scope. Running a pre-mortem before the scope debate could reframe the conversation away from "who wins" toward "what actually puts the launch at risk."
- Adaptation needed: At Meridian, the pre-mortem was run async via a shared doc and synthesized before the meeting. At Volta, relationships are more contentious — Kate may need to run it live and as a joint exercise to prevent each team from writing a pre-mortem that blames the other.
- Risk: If Volta's VP of Engineering feels the exercise is being used against engineering, it could backfire. Kate needs to frame it as shared risk discovery, not a veto mechanism.
Technique 2: The "what does good look like in 90 days?" alignment anchor
- What works: At FLUXX, Kate started each steering committee meeting by asking every stakeholder to write a sentence completing "In 90 days, this initiative will have succeeded if ___." The variance in answers surfaced misalignment the committee had been papering over for months. It's now a standing opener.
- Could apply to: Meridian Health — exec team has competing priorities but hasn't explicitly surfaced what they disagree on. The FLUXX opener is low-threat and can be run in a 30-minute working session before the next roadmap review.
- Risk: Meridian's CEO tends to set the frame early in meetings and others converge. Kate should collect written answers before anyone speaks.
Contradictions
Contradiction 1: Top-down priority mandates
- The split: At FLUXX, Kate recommended the transformation leadership team issue a clear, public priority mandate (transformation initiatives take precedence over BAU when they conflict). It reduced ambiguity and gave middle managers something to point to when declining work. At Volta, a similar mandate from the CEO ("shipping beats perfect") has made engineers feel steamrolled and is actively increasing GTM/engineering tension.
- The variable: Organizational trust level and mandate history. FLUXX's teams had been asking for clarity for 18 months — a mandate was permission they wanted. Volta's engineering team has a history of being overridden and feeling burned by rushed releases; another top-down mandate read as confirmation of a pattern, not resolution of one.
- The lesson: Top-down clarity works when it resolves ambiguity people have been asking to resolve. It backfires when it resolves ambiguity in a way that confirms one team's fear that they don't have real input. Kate should assess "have they been asking for a call or asking for a seat at the table?" before recommending mandates.
Content Opportunities
Theme 1: Prioritization frameworks don't fail — commitment structures do
- Evidence from: Meridian Health, Volta Infrastructure, FLUXX Financial (all three in the same 30-day window)
- Content angle: Every client is running a recognizable prioritization process. None of them are broken at the framework level. They're broken at the "what actually changes after we leave the room" level. Kate has three simultaneous data points on this, which means she can write about it as a structural consulting observation, not a single engagement anecdote. Strong angle for a LinkedIn post or a short essay: "The problem with your prioritization process isn't the framework."
Theme 2: Middle management as the implementation gap
- Evidence from: FLUXX Financial (explicit resistance), Meridian Health (roadmap decisions not cascading to team leads), Volta Infrastructure (GTM/engineering misalignment living at the director level)
- Content angle: All three clients have executive alignment and team-level execution capacity. The gap is the layer in between. Kate has a differentiated POV here — most transformation content focuses on exec buy-in or team enablement. The middle layer is under-covered.
Action Items
-
Before the Volta alignment meeting on June 24th: Run the pre-mortem exercise live with both the GTM and engineering leads. Adapt the Meridian async format to a 25-minute facilitated session. Send a framing note to Volta's CPO this week to get buy-in on the approach before the meeting.
-
Bring the FLUXX "90-day success" opener to Meridian's next exec session (June 19th): Send the question in writing to all three execs 24 hours in advance so the CEO doesn't set the frame verbally before others can respond. Compare answers in the meeting.
-
Draft the prioritization content piece this week while the pattern is fresh: Three active clients, same structural problem, 30-day window. The "commitment structure" framing is specific enough to be credible and broad enough to resonate. Target 600–800 words. Publish before the end of June while the observations are current.