For TPMs

You run the program but manage none of the people. Every outcome you own routes through teams that don’t report to you, priorities you don’t set, and a weekly status update that half your stakeholders skim and the other half misread. The work that makes programs succeed — unblocking, aligning, chasing the orphaned problem nobody owns — is precisely the work that’s hardest to point at come review time. Being essential and being seen are, frustratingly, different problems.

bettersense treats both as real.

Your starter kit

Five things. Start here.

	When it fires	What it does for you
the-program-manager	Running anything multi-team, multi-month	Dependency mapping, risk gates per phase, go/no-go criteria, escalation framing — program mechanics as a discipline, not vibes.
influence-without-authority	”I need Platform to prioritize this and I’m not their boss”	Coalition-building, positions vs. interests, sequencing the asks — opinionated about the line between influence and manipulation.
the-status-crafter	The weekly/monthly update	Status that provides signal: honest RAG with evidence, decisions explicitly requested, risks actually named. Catches watermelon status before your stakeholders do.
stakeholder-reflect	After the steering meeting	Your program lives on relationships with people you don’t manage. Dated reflections on the skeptical principal, the checked-out sponsor, the ally you’re under-using.
weekly	Friday, 15 minutes	Wins captured (including the invisible unblocking work), one overdue stakeholder reflected on, cross-program patterns surfaced.

A week with bettersense

Monday. An issue has been bouncing between two teams for three weeks; both think the other owns it. the-program-manager helps you adopt it formally — owner, decision needed, date — and frame the escalation so it reads as clarity, not blame.

Wednesday. You need the data platform team to move your migration up a quarter. influence-without-authority maps who actually influences their roadmap, what their problem is, and which order to have the conversations in. The answer is not “email their manager.”

Friday, 2pm. the-status-crafter assembles the weekly update — and flags that you’ve reported zero risks three weeks running on a hard program, which reads as either luck or silence. You add the real one. At 3pm, /bettersense:weekly: the two-team unblock gets logged as a win with named evidence, because in six months nobody will remember it happened — including you.

When you’re ready for more

• The glue problem: glue-audit quantifies the invisible coordination work you do; wins-curate turns the log into a review-ready case that frames it as leadership, not overhead.
• Reading the room: read-the-room for the steering meeting where everyone nodded and nothing was agreed.
• Risk discipline: premortem before every major phase gate — solo or facilitated with the team.
• First-time setup: run /bettersense:start — profile, one stakeholder, this kit.