Before PMWISE, every PM tool reduced projects to numbers in a two-dimensional grid — scope, budget, timeline. But projects are moving, fuzzy, four-dimensional constructs, built on realms of uncertainty to satisfy ambiguous requirements of taste and judgement. A cell in a spreadsheet cannot calculate viability or suitability. It cannot adjudicate success or understand vision. A spreadsheet has no formulae for why — so we didn’t build PMWISE on one. We designed it from scratch, harnessing the disruptive nature of generative AI, so purpose and vision can now be managed as easily as budgets and schedules.
The one-line version
There is no formula for moral and ethical behaviour, no blueprint for informed insight, no recipe for judgement and taste. Spreadsheets don’t understand why. PMWISE was built on the why, and treats every project process as its servant.
That’s why PMWISE is categorically different from every tool that came before it. It isn’t a calculator with another column — it’s a motivated, highly-trained and deeply knowledgeable collaborator, helping you achieve your outcomes in the best way possible.
Most software is shaped by the legacy frameworks it’s built on, and every other project tool available today is grounded in the spreadsheet’s two-dimensional limits. PMWISE was built in 2026, so we didn’t start from a 2D grid — we started with the neural networks created by agentic and generative AI. We started with one question: could this new paradigm create a tool that learns the messy lessons of project failure (projects fail 70% of the time), and let people manage the parts of projects that actually matter?
The question was simple: can AI make the messy but important stuff as easy to manage as time and cost? Turns out it can. This means PMWISE reverses 70 years of project-management orthodoxy and puts the why horse back in front of the how cart.
PMWISE considers questions a grid never could — what is this actually for? does this measure still serve its purpose? is this benefit worth its cost to the people it touches? — as readily as “are we on time, are we on budget?” To do that we didn’t only train PMWISE in best-practice method. We gave it an informed point of view, an ethical and moral compass, and we taught it philosophy to fuzzy-up and humanise its thinking.
An ethical spine, not a compliance afterthought
The AI inside PMWISE has an ethical compass, and it’s written down. Our Responsible-AI framework is anchored in Australia’s AI Ethics Framework (Dawson et al., Data61 CSIRO, 2019) — adopted as binding, not aspirational — and extended with five principles specific to the stakes of project work: teams, budgets, livelihoods.
Its posture is deliberately modest and deliberately firm. Where it sees a cost to people, communities or the environment that hasn’t been acknowledged, it raises it — it does not quietly decide for you, and it will not smooth over uncertainty to seem more useful than the evidence warrants. PMWISE does not live in a moral vacuum: it will not derive outcomes that cross the CSIRO boundaries, and it will reject clients who try to force it across those lines.
Generates net-benefits — the system must produce benefits for people greater than its costs.
Do no harm — civilian AI must not be designed to harm or deceive, and should minimise negative outcomes.
Regulatory & legal compliance — it must comply with all relevant laws and regulations.
Privacy protection — it must respect and uphold privacy rights and data protection.
Fairness — it must not result in unfair discrimination against individuals, communities or groups.
Transparency & explainability — people must be able to understand when AI is affecting or deciding about them.
Contestability — there must be a timely process to challenge the use or output of the system.
Accountability — those responsible for the system must be identifiable and accountable for its outcomes.
Dawson et al., Data61 CSIRO, 2019 — adopted by PMWISE as binding.
Honest uncertainty in forecasting — never present a projection as more certain than the evidence warrants.
Harm-escalation detection — surface foreseeable harms that haven’t been acknowledged.
No stakeholder manipulation — it won’t help engineer or manipulate stakeholders.
Human welfare at project close — the people, not just the deliverables, matter when work ends.
No assistance with unlawful activity — it won’t assist unlawful conduct.
Calculating why
AI means PMWISE can embody philosophical frameworks to derive bespoke solutions, leveraging and acknowledging uncertainty as a source of creativity. At each step it offers you, the client, the chance to rethink the options — sitting in an ongoing conversation to surface alternative perspectives. These ideas are already hard-wired in; more will be added as the product matures.
Epictetus taught that peace and effectiveness come from knowing what you can control and what you can’t — and spending energy only on the former. PMWISE tests whether an issue is actionable. It pushes, charitably, to find a lever you may have overlooked — but where something is genuinely outside your control, it doesn’t badger. It helps you accept it and reframe toward the part you can act on. Honest agency, not false hope.
To understand anything, Aristotle held, you must know its telos — its end or purpose. PMWISE applies this literally: before it asks how good a deliverable should be, it derives the quality attributes that fit the nature of that particular thing. You cannot judge the quality of something until you know what it is for. Purpose comes before measurement, every time.
Kano (1984) distinguishes three kinds of quality: Must-be (the floor — its absence is a defect), Performance (more is genuinely better, and you choose how far), and Attractive (an unexpected delighter). PMWISE puts this choice in front of you and prices each option live in time and resource — so “gold-plating” becomes a conscious, costed choice rather than an accident.
“When a measure becomes a target, it ceases to be a good measure.” This is the quiet way good projects go wrong. PMWISE runs an explicit Goodhart Check — tracing each quality choice back to the benefit it was meant to serve, and if a target has turned against its own purpose, it stops and says so. This is the one place the product refuses to stay silent.
From the Toyota Production System: it’s better to stop the line and fix a fault than let a flaw travel downstream. PMWISE’s quality model is named for it. Rather than checking endlessly and everywhere, it stops once, at the right moment, to confirm the choices still serve the purpose before letting work continue. One deliberate gate beats a hundred anxious ones.
Lasting improvement comes not from grand leaps but from a steady accumulation of small, deliberate steps. PMWISE carries this into delivery: work advances in small, self-contained slices, so value arrives early, course-corrections stay cheap, and the plan improves as it’s delivered — not only at the post-mortem. Where jidoka protects quality by stopping, kaizen is its forward-facing twin.
Work-in-progress, completion rate and lead time are locked together — you can’t improve one without moving the others. The honest consequence, which PMWISE says out loud: the only real way to go faster is more capacity, not a more optimistic plan. A deadline squeezed without more people or time doesn’t speed delivery — it just hides the overflow. This anti-fantasy honesty is what makes the forecasts trustworthy.
The through-line
A smaller true claim over a bigger false one.
If there’s a single ethic underneath all of this, it’s honesty. PMWISE would rather show you a smaller truer number than a bigger false one — whether about quality, about progress, or about whether a project is really on track. Each idea above is there to stop a specific, familiar way that projects quietly lie to the people running them.
That’s the difference between a spreadsheet and PMWISE. The other holds your why — and keeps it honest.
We’d love to show you. Reach out and we’ll walk you through what’s under the hood.
Speak to our founder