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
A plan tells you what you agreed to. It rarely tells you why it changed.
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."
Why, not just whatEvery change carries the reason it happened, next to the change itself.
Settled stays settledThe argument you finished in March does not come back in June.
A slip has a causeYou can tell a date that moved for a reason from a decision that went wrong.
A real day
Five spreadsheets, one Jira board, and a daily that took an hour.
A TPM keeps the big rocks in one sheet and four parallel initiatives in four more. Every morning she reads the Jira board to the team, then copies their progress into each sheet. She asks them to update it themselves, but nobody knows which file. Decisions go out in a chat message and an email. That afternoon, when she sits down with the director and the tech lead, everyone has their own version, and some commitments are simply gone.
"Which file do I update?"
One plan for everything
The big rocks and every initiative live in one workspace, pulled from Jira with the history of every date. Nobody copies progress into a sheet, and nobody has to guess which one.
A one-hour daily
The daily starts from what changed
Each person confirms their own milestones from their phone before the meeting. The daily covers what moved and what needs a word from someone, not the whole board read aloud.
Decisions lost in chat and email
Paste the notes, keep the commitment
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.
"Everyone has their own version"
The director reads the same record
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
Everything around a plan, in one place.
Why every date moved
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.
Risks with no plan, first
Open risks ranked by the milestone they threaten and when, each with an owner - and the ones nobody has answered at the top.
When it will really land
Next to every committed date, the date it is likely to finish - learned from how your own team's milestones have finished before.
theruKO reads the plan and writes the update
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.
Ask Claude or Cursor about your plans
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.
The weekly update is the meeting
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
The plan, the report and the answer are three copies of the same thing.
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 once
Dates, 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 - read
The 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.
Access is by invitation for now
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
This is your plan, minutes after you upload it.
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.
A sample workspace, unedited: 14 risks across four projects, traced to what caused them and what was decided about each.
Where it fits
It works with the plans you already have.
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.
Your files, not a new formatExcel, CSV, MS Project, Word, PowerPoint, PDF or pasted text in - reports out as PDF
Your data stays yoursNothing is shared until you share it, and there is no lock-in
Compared with what you use today
What Decision Memory adds to the tools you already have.
Excel with an AI assistant
Copilot or Claude answers from whatever you paste in today.
No memory of last month's plan, or why it changed.
+
Jira
Tracks the work, ticket by ticket.
Not the dates you promised, or why they moved.
Decision Memory
With Decision Memory
On top of your AI assistant
Every version of the plan kept: what moved, from when to when, why, and who decided.
Every moved date asks for its reason, tied to the risk, mitigation or decision behind it.
theruKO answers from that history - and nothing changes until you approve it.
Your team and executives read one live plan through links you control.
On top of Jira
Every date a Jira pull brings in is kept, with theruKO's suggested reason.
One portfolio view across Jira, Monday and spreadsheets.
A weekly update and an executive report read without opening Jira.
Read-only: Decision Memory never writes back to Jira.
So it knows why you are where you are.
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
The three questions everyone asks first.
Do I have to give up my spreadsheet, or Jira, or MS Project?
No. Decision Memory sits above whatever you already run rather than replacing it - your team keeps working where they work. Bring a plan in from Excel, CSV, MS Project (saved as XML), Word, PowerPoint, PDF or pasted text, or connect Jira or Monday: the work comes in with the history of every date, and stays in step when you pull. The connection only reads - Decision Memory never writes back to Jira or Monday.
Who else has to approve this before I can try it?
Nobody. Free is two people, one portfolio and one project, sign in with Google - no card, no install, nothing for IT to deploy. You can load your own plan this afternoon and decide on your own evidence. Bring the PMO in later, once you have something worth showing them.
Where does my data live, and can I get it back out?
In your own workspace, private by default: nothing is visible to anyone else until you deliberately share it, and every share is a link you control and can revoke. Reports print to PDF from inside the product, and if you ever want a full copy of your data, ask us and we will send it. Enterprise adds a security review for organizations that need one before they can say yes.
Your data stays in your workspace
No sharing without your permission
Your data back whenever you ask - no lock-in
Company
Theruka keeps strategic work from disappearing into meetings, files, and chat history.
