Project and portfolio memory
For PMOs and programme leads who answer to executives for several projects at once.
Every organization keeps its plans - in spreadsheets, slide decks, and a project tool nobody updates. Almost none of them keep the reasoning: why a date moved, which risk caused it, who decided. Theruka Decision Memory keeps both, so strategic work stops disappearing into meetings, files, and chat history.
Every Max feature for 14 days. No card, nothing to install - start with the spreadsheet you already have.
Decision memory
Six months in, the dates are different, three assumptions have quietly moved, and the file that explains any of it was never written. So the same question gets re-argued every quarter, and a slipped date looks exactly like a bad decision.
Decision memory is the missing half: the record of why the plan is what it is, kept next to the plan itself. It turns "this is late" into "this is late because we chose the pilot over the full rollout in March, and here is what we did about it."
A real day
A TPM tracks the big rocks in one sheet and four parallel initiatives in four more. Every morning she reads the Jira board aloud, then copies everyone's progress into each sheet by hand. Decisions go out in a chat message and an email. By the afternoon meeting with the director and the tech lead, everyone has their own version, and some commitments are simply gone.
"Which file do I update?" Progress lives in five sheets, and the TPM copies it across by hand every morning.
The big rocks and every initiative live in one workspace, pulled from Jira with the history of every date. Nobody copies progress, and there is no file to guess.
An hour spent reading the whole Jira board aloud.
Before the meeting, each person confirms their own milestones from their phone. The daily covers only what moved and what needs someone's decision.
Decisions scattered across chat and email, and some commitments never reach the plan.
Paste the meeting notes or the chat thread. theruKO turns them into dated commitments, each with its reason and the risk behind it, and nothing is saved until you approve it.
The director, the tech lead and the TPM each bring their own version.
The Program Review shows every initiative: what moved, why, and what is still open. It is the record the team keeps every day, so there is no other version to argue about.
Same people, same Jira. The daily is about what changed, and the afternoon review starts from one version of the commitments.
What you get
Each move keeps its reason, the risk behind it and who decided. "Why is this late?" takes ten seconds, and everybody gets the same answer.
Open risks ranked by the milestone they threaten and when, each with an owner - and the ones nobody has answered at the top.
Next to every committed date, the date it is likely to finish - learned from how your own team's milestones have finished before.
theruKO is the AI assistant built into Decision Memory. Drop in Excel, MS Project, Word, PowerPoint or PDF and it becomes milestones, owners and risks; then theruKO drafts the weekly update and answers "why did this move?" It runs on your plan's monthly AI credits.
On Max: connect Decision Memory to Claude or Cursor, sign in, and ask "what needs my attention?" or "why did this slip?" It reads your plans and can refresh them from Jira, but never edits them itself.
One page a week. Owners answer from their phone, the report is ready to print, and Slack or a weekly email reaches whoever never opens a dashboard.
One version of the truth
That is where the friction comes from. The plan lives in one tool, the report is rebuilt by hand in another, and the answer to "why did this move?" is reconstructed from memory in the meeting itself. Three artefacts, maintained separately, disagreeing quietly - and the executive is the one who finds out they disagree.
The plan
Kept onceDates, owners, dependencies and risks in one place - imported from the plan file you already have, or pulled from Jira or Monday with the history of every date, so it stays in step with where the work actually happens.
The report
Not rebuilt - readThe executive view is the plan, arranged for somebody who has ten minutes: what moved, what caused it, what is still unanswered and how long it has been open. Nobody assembles it, so it cannot be out of date or quietly flattering.
The question
Answered from the same record"Why is this three weeks later than March?" is answered by the plan itself, in front of everybody, with the risk that moved it and what was decided. Not from a memory that flatters whoever is speaking.
When those three stop being separate documents, the arguments they used to cause stop happening. The meeting is about what to do next, rather than about whose version of last quarter is right.
By the second month, "why is this late?" is a ten-second answer instead of a two-day search through files and chat history - and the answer is the same one everybody sees.
Theruka Decision Memory is in pre-launch. Join the waitlist and we will email you when your access is ready: on Free, which does not expire, or with early access to Max.
Early access means the Max plan's features, no charge, no end date, until paid plans open. Your data stays, and we will tell you at least 10 days before early access ends and what you can choose then.
How it works
Bring the spreadsheet your team already argues over, or paste the plan as text. Decision Memory reads the milestones, dates, owners and risks out of it and builds the executive view for you - then keeps the reason attached to everything that changes afterwards.
Start your 14-day free trialWhere it fits
You do not migrate anything or ask anyone's permission to start. Upload one plan, keep using the spreadsheet next to it if you want, and see whether the second month is calmer than the first.
Compared with what you use today
Copilot or Claude answers from whatever you paste in today.
No memory of last month's plan, or why it changed.
Tracks the work, ticket by ticket.
Not the dates you promised, or why they moved.
With Decision Memory
What caused the delay, which reason keeps coming back, which milestone dragged which, whether the mitigations worked - and where the plan is heading.
Before you try it
Company
