in development
KISS PM / Product case study
Project decisions you can review before they change the plan
KISS PM turns a project goal or problem into a structured proposal, lets you review the before-and-after impact, and applies only the changes you approve.
For project and delivery teams with a real planning problem.
01 / The challenge
Seeing project status is not the same as safely changing it.
A delayed task can affect dependencies, resource load, the project finish date, and a client promise at the same time. The manager usually has to collect that context manually, rebuild the plan, update assignments, and explain what changed.
AI chat alone does not close the gap. A useful answer still has to become a safe, reviewable change in the project system.
02 / The governed loop
The agent is a working layer over the project model.
It gathers context and prepares the change. The person responsible for the plan decides what is allowed to happen.
- 01 Describe the goal
- 02 Read project context
- 03 Prepare a proposal
- 04 Review the impact
- 05 Apply approved changes
- 06 Create a plan commit
- 07 Record the audit event
Goal → context → proposal → review → apply → plan commit → audit
03 / Real product surfaces
One model, seen from the decision that needs to be made.
Portfolio, schedule, capacity, and risks are connected context for the same operational decision.
Portfolio
Several projects, one operating picture.
A compact portfolio view keeps project status, dates, value, planned hours, and lifecycle actions in one place.
Planning
The schedule is a working model.
Tasks, work packages, dependencies, effort, milestones, baseline, and critical path share one planning surface.
Capacity
A conflict has a person and a date.
Daily capacity and scheduled work reveal the exact person and date behind an overload.
Signals
Calculations become next actions.
The project overview converts planning calculations into clear signals and direct follow-up actions.
04 / Agent in action
The consequential moment is review, not chat.
“Resolve the overloaded resource and keep the delivery date safe.”
Henry Gantt scans capacity and active assignments, compares safe options, and prepares a proposal. Nothing changes until the selected action is applied.
Before Ready for review
After Applied with receipt
Screens 06–08 are English presentation reconstructions of a verified execution. A deterministic reasoning provider was used for reproducibility; proposal review, permissioned apply, plan versioning, commit creation, and audit recording were application behavior.
05 / Versioned result
An approved action becomes durable project history.
The commit records when the change happened, where it came from, which work was affected, and which audit event was created.
06 / Current status
Built enough to test the workflow. Still early enough to shape it.
Ready to show
- Connected portfolio, planning, capacity, and signal surfaces
- Human-reviewed proposal and apply flow
- Versioned execution, commit, and audit evidence
In progress
- Product hardening
- Integration work
- Private-beta validation in real operating contexts