alynOS · Alignment & Execution Diagnostic

Executive summary

Effort is broadly mis-aligned with the declared priorities: the initiatives that matter most are either starved or stalled, while undeclared work absorbs roughly a third of senior attention.

Key findings

Attention is leaking. About a third of leadership attention (34%) goes to undeclared work, led by the Northwind custom build at 19%, which alone outweighs three of the five declared priorities.
The top priority is attended but not advancing. Enterprise Tier Launch draws the most attention, yet 57% of it is remedial, with the same enterprise-GA decisions reopening week after week.
Two heavy priorities are under-served. NRR Recovery is under-attended and Platform Reliability is structurally starved with no senior forum, while a moderate priority (Onboarding) outdraws both.

Likely next steps

Run one decision Workout on the Enterprise launch. Validate the read, then settle the contested SOC2 and GA-gate calls and shrink the 16-person sync into a small decision forum.
Give the starved priorities standing senior attention. Stand up a reliability review and name a single owner for the retention and expansion motion.
Decide on Northwind at ExCo. Formally prioritise it or contain it, so it stops drawing senior attention by default.

Layer 1 shows whether effort is directed at the declared priorities. Layer 2 examines, for the work that is receiving attention, whether it is advancing or stalling, and converts each finding into a scored, validated sprint.

Confidence High Med Low

Advancing attention is productive

Remedial-dominated attended, but largely remedial

Starved under-attended vs intent

Leak attention off the priority list

Portfolio attention map

role-weighted talk-time + calendar · relative to declared intent

Declared initiative	Intent	Attention (advancing / remedial)	Tier read	Status
Enterprise Tier Launch INIT-01	MAX	43% advancing 57% remedial · 22% of attention	senior-heavy	Remedial-dominated
Net Revenue Retention Recovery INIT-02	HEAVY	70% advancing 30% remedial · 9% of attention	moderate	Under-attended
Platform Reliability (99.9%) INIT-03	HEAVY	62% advancing 38% remedial · 6%, IC-tier only	no exec forum	Starved
Onboarding Time-to-Value INIT-04	MOD	78% advancing 22% remedial · 12% of attention	senior-heavy	Advancing
Pricing & Packaging Refresh INIT-05	LIGHT	80% advancing 20% remedial · 3% of attention	low	As intended

LEAK

34% of measured leadership attention went to work that is not on the priority list at all.

The largest single block, about 19%, is a bespoke build for one prospect ("Northwind custom"). It draws more senior attention than INIT-02, INIT-03 and INIT-05 combined, and was never declared a priority.High this is a count, not a judgement.

INVERSION

A MOD initiative is out-drawing two HEAVY ones.

Onboarding TTV (INIT-04, intent MOD) pulls more senior attention than NRR Recovery and Platform Reliability, both HEAVY. Reliability has no standing exec forum on the calendar, a structural starvation signal rather than just low airtime.Med verify the quiet initiatives are not simply progressing with little discussion.

Intent tags are coarse by design (MAX / HEAVY / MOD / LIGHT). Findings are relative: leak share and rank inversions, so no numeric target is required, and a LIGHT item drawing little attention reads as correct rather than starved.

Initiative read

click any initiative to expand · execution, blockers, scored interventions, validation

MAX Enterprise Tier LaunchINIT-01 22% of attention · 57% remedial Remedial-dominated Med ▶

Attention rank

#1 of 5matches MAX intent, allocation is correct

Advancing vs remedial

57% remedialrecurring remedial work, not progress

Split confidence

Medqualitative read

⚑

The concern is not under-resourcing. This is the most-attended initiative in the company, which is correct, but most of that attention is remedial and recirculates the same unresolved issues. The advancing/remedial split is a qualitative read at medium confidence, so it is routed to the validation sprint before any fix is committed.

Diagnosed blockers · mechanism-specific, evidence-linked

BLK-01-A

No one owns the SOC2 scope decision, so it reopens every week

Compliance and Engineering each believe the other holds the call on how much SOC2 scope ships for GA versus fast-follow. The decision keeps reopening instead of sticking.

High▶

Signals · recurrence is the strongest of these

#enterprise-launchSame scope question reopened in 6 of the last 9 weekly syncs. "Are we gating GA on full SOC2 or not, thought we closed this?" [Eng Lead], wk of 18 May

transcript · 3 mtgs"That's Compliance's call." and "We've been waiting on Eng to decide what's feasible." Circular ownership, two roles, same week.

escalation · emailTwice escalated to [COO] for a tie-break, with no durable decision recorded afterward

BLK-01-B

Sales pre-sells uncommitted features, and comp rewards the booking

Enterprise dates land in contracts before Product agrees them. The mechanism is the incentive: bookings are rewarded, roadmap over-promise carries no cost.

Med▶

Signals

deal-desk · 2 threadsTwo enterprise deals carry contractual feature dates Product has no record of committing to

#product-eng"Did we actually commit to SSO by Q3, or did the deal just say so?" Recurring question, [PM].

model noteLower confidence: an incentive inference. Anonymisation masks whether this is two reps or a systemic comp issue, so it is flagged for interview.

BLK-01-C

The launch sync has bloated into a status readout, and decisions leak into DMs

Grew from 6 to 16 attendees. About 80% of airtime is reporting. Real decisions get deferred, then made informally afterward.

High▶

Signals

calendarRecurring "Enterprise Launch Sync" attendee count grew 6 to 16 over the window

transcriptAbout 80% of speaking time is sequential status updates. Decision moments deferred with "let's take it offline."

DM trailKey calls resurface as 1:1 DMs hours later. Decisions get made, but not in the room or the record.

Candidate interventions · each scored independently (one diagnosis, 2 to 3 rituals)

Decision-Rights Workout, scoped to the 3 contested calls only

Leader frames and leaves. Room assigns a single named owner for the SOC2-scope call, the GA-gate call, and the fast-follow line. Decisional close, 75% rule, named observer reporting to steerco. Fixes BLK-01-A.

PRIORITY 1

cure confidence impact High effort to fix Fast durability mechanism-backed

Decision-forum redesign, sunset the readout

Cut the sync to a 5-person decision forum. Status moves async. Decisions get made and logged in the room. Fixes BLK-01-C. Same friction theme as Priority 1, so the two fold into one sprint.

PRIORITY 2

cure confidence impact Mod to High effort to fix Fast

"Commit gate" mechanism for contractual feature dates

No feature date enters a contract without a named Product owner's written sign-off. A lightweight ritual that addresses the symptom of BLK-01-B without touching comp.

PRIORITY 3

cure confidence impact High effort to fix Moderate

Comp-plan change, reward deliverability alongside bookings

The root of BLK-01-B. This is a structural compensation change, not an in-room ritual, so it sits outside what an alynOS Workout can install. Routed up as a recommendation rather than scoped as a sprint.

OUT OF SCOPE → ExCo

cure via ritual Low impact High effort to fix Slow, hard limit named, not buried

Validation sprint · scaled to confidence

REQUIRED · not skippable ~1 week because BLK-01-B is medium-confidence on a fix that is expensive and contested, and the 57% remedial read needs a human check. BLK-01-A and -C are high-confidence and cheap, so they could proceed unvalidated, but are folded into the same week for efficiency.

Who (role · tier)	Name	What this interview is for
Eng Lead · senior	to be named	Confirm who they believe owns the SOC2 call (BLK-01-A)
Compliance Lead · senior	to be named	The same question, from the other side of the collision
VP Sales · senior	to be named	Is the pre-selling two reps or the comp plan? (BLK-01-B)
Product owner · mid	to be named	Confirm the uncommitted-dates pattern is real and recurring
IC on launch · ground	to be named	Confirm the advancing/remedial split as lived experience

Humans confirm and name. The model detects the pattern blind, the facilitator re-attaches identity and intent. Names assigned at the transformation office's discretion.

Interview probes

Confirm the read: "Roughly 57% of this initiative's airtime looks remedial rather than advancing. Does that match your week?"

Resolve ownership: "When the SOC2 scope question comes up, whose call is it, honestly?"

Test the mechanism: "Is over-promising a couple of reps, or what the comp plan rewards everyone to do?"

Resulting sprint backlog

SPRINT 1
now

Enterprise-launch decision-clarity validationvalidation1 wk

The 5 interviews above. Output: confirmed, revised or killed on each blocker, names attached, and a friction sentence sharp enough to drop straight into Sprint 2.

SPRINT 2
on pass

Enterprise GA Decision Workoutfix6 wk

One friction theme, "who decides what ships for enterprise GA." Installs decision rights for the 3 contested calls (BLK-01-A) and redesigns the bloated sync into a 5-person decision forum (BLK-01-C). 30/60/90 with a named observer reporting to steerco.

PARALLEL
ExCo

Commit-gate ritual, plus comp-plan recommendationescalation

Stand up the commit-gate mechanism now (BLK-01-B symptom). Route the comp-plan root cause to ExCo as a recommendation, since it sits outside ritual scope.

HEAVY Net Revenue Retention RecoveryINIT-02 9% of attention · below HEAVY intent Under-attended Med ▶

Attention rank

#4 of 5well below its HEAVY intent

Advancing vs remedial

30% remedialwhat attention it gets is productive

Read confidence

Medcould be quiet execution

⚑

A HEAVY priority getting MOD-level attention. Under-attention can indicate a real gap, or simply quiet, focused work that generates little talk-time, so this finding is held at medium confidence and relies on the validation interview.

Diagnosed blockers

BLK-02-A

The expansion motion has no owner

CS treats retention as support, Sales treats it as post-sale. Proactive expansion falls between them and happens only ad hoc.

Med▶

Signals

#customer-successTwo at-risk accounts saved late, both handled reactively with no standing owner named

QBR cadenceExpansion conversations appear only when a renewal is already in question, not on a forward cadence

BLK-02-B

No standing retention forum on the calendar

Renewal risk surfaces late because nothing reviews it on a regular cadence.

High▶

Signals

calendarNo recurring renewal or retention review across the 90-day window

Candidate interventions

Ownership Workout for the expansion motion

Name one accountable owner across the CS and Sales boundary. Fixes BLK-02-A.

PRIORITY 1

cure confidence impact Higheffort to fix Moderate

Stand up a monthly renewal-risk review

A cadence mechanism so risk surfaces early. Fixes BLK-02-B.

PRIORITY 2

cure confidence impact Modeffort to fix Fast

Validation sprint

REQUIRED~1 week · 3 interviewsto confirm the under-attention is a real gap and not quiet, healthy execution before standing up new forums.

Interview probes

Test the gap: "NRR Recovery is drawing about half the attention we'd expect for a HEAVY priority. Is that because things are quietly on track, or because the motion has stalled?"

Test ownership: "When a renewal is at risk today, who owns the recovery conversation — CS or Sales?"

Test the cadence: "Is there a forum where upcoming renewals get reviewed proactively, or does risk surface only when someone raises it?"

Resulting sprint backlog

SPRINT 1
on pass

Retention ownership and cadencefix4 wk

Name a single cross-functional owner for expansion and renewals, and stand up a monthly risk review. Conditional on validation confirming the gap is real.

HEAVY Platform Reliability (99.9%)INIT-03 6% of attention · no exec forum Starved High ▶

Attention rank

#5 of 5HEAVY intent, lowest attention

Tier

IC onlyno senior presence, no standing review

Read confidence

Highcalendar is a count

⚑

A structural starvation signal, not just low airtime. There is no exec-tier forum for reliability anywhere on the calendar, so incidents are handled reactively by on-call and reach leadership only after the fact. High confidence because the absence of a forum is observable, not inferred.

Diagnosed blocker

BLK-03-A

No leadership forum or owner above on-call

Reliability has no accountable owner at the exec tier and no standing review. Incidents are handled reactively, then drop out of sight.

High▶

Signals

calendarNo recurring reliability or incident-review meeting at any senior tier

#incidentsThreads spike during an incident, then go quiet with no post-incident owner or follow-through

Candidate intervention

Stand up an exec-tier reliability review, name an owner

A cadence and ownership mechanism that gives reliability standing senior attention and a single accountable owner. Fixes BLK-03-A.

PRIORITY 1

cure confidence impact Higheffort to fix Fast

Validation sprint

SKIP-ELIGIBLEby mutual agreementhigh-confidence diagnosis, cheap and reversible fix. Standing up a recurring review costs little and is easy to unwind, so this can go straight to the fix sprint if the transformation office agrees.

Resulting sprint backlog

SPRINT 1
now

Reliability owner and exec review cadencefix2 wk

Name an exec-tier reliability owner. Stand up a bi-weekly review covering uptime trends, open incidents, and the 99.9% path. Skip-eligible validation means this can start immediately.

MOD Onboarding Time-to-ValueINIT-04 12% of attention · above MOD intent Advancing High ▶

Attention rank

#2 of 5above its MOD intent

Advancing vs remedial

22% remedialhealthy, work is moving forward

Read confidence

High

✓

Execution is healthy and there is no blocker worth a sprint. The only signal is allocation: this MOD initiative is drawing senior attention that outweighs its declared intent, and it currently out-ranks two HEAVY priorities. Worth monitoring, but the work is moving. No sprint recommended; monitor allocation only.

Watch signal · no sprint required

WATCH

Allocation is above intent, but execution is clean.

This initiative is not stalling and has no diagnosed blocker. The allocation concern (a MOD drawing senior-level attention ahead of two HEAVY items) is a portfolio-level signal, already captured in the L1 inversion flag. No dedicated intervention here; monitor whether attention normalises as the two starved HEAVY priorities receive their own standing forums.

Validation sprint

NOT REQUIREDhigh-confidence advancing read; no contested blocker to validate.

LIGHT Pricing & Packaging RefreshINIT-05 3% of attention · matches LIGHT intent As intended High ▶

Attention rank

#3 of 5proportionate for LIGHT intent

Advancing vs remedial

20% remedialclean, work is on track

Read confidence

High

✓

A LIGHT priority attracting LIGHT attention, with a healthy advancing split. This reads as correctly calibrated. No anomaly, no blocker, no sprint. Note that for LIGHT intent items, low attention is correct rather than starved, and is recorded as such.

No intervention required

This initiative is executing as intended. It will re-enter the diagnostic at the next run window. If the declared intent changes (e.g. elevated to MOD or HEAVY), the attention read would need to be reassessed.

Validation sprint

NOT REQUIREDas-intended read, high confidence, no contested blocker.