The Cisely Way
Alignment is not something you reach. It is something you design.
Most value is built when demand and supply believe in the same thing. That coincidence almost never happens on its own, and it cannot be held in a document — so Cisely keeps two connected graphs, a business context graph and an engineering context graph, and runs a loop across them that makes alignment reachable and hard to lose. Six stages, and it genuinely closes.
The loop
Each stage says who holds what. That division is the method: you supply judgement and conviction, Paroksh supplies the drafting and the building, and neither does the other’s job.
Stage 01: Say what you believe
Not a mission workshop. A conversation, in which you are asked things only you can answer — what you hold true, who you are for, what you refuse to do.
- You
- Bring the conviction, and the answers nobody else has.
- Paroksh
- Asks what is missing, then drafts the mission, the beliefs and the strategy.
The gateEvery belief carries a conviction level: assumed, observed or validated. A guess is allowed — a guess dressed as a fact is not.
Stage 02: Activate what you agree with
Everything Paroksh drafts arrives as a draft. You read it, change what is wrong, and activate the rest. Until you do, it is a proposal.
- You
- Read, correct, and activate. This is the judgement, and it is not delegable.
- Paroksh
- Revises against what you said, and leaves the rest alone.
The gateNothing enters the model because it was plausible. It enters because a person said so.
Stage 03: Name the promise
A persona in a situation is trying to achieve something. The measurable version of that is an expectation — the promise the business is making, in a form that can later be checked.
- You
- Decide what you are actually promising, and to whom.
- Paroksh
- Turns goals into expectations that a metric could measure, and says when one cannot.
The gateAn expectation that no metric could ever measure is a feeling. The model asks you to write the measurable version.
Stage 04: Build what keeps it
A project reads the business context graph you activated and grows the engineering context graph against it — the plan, the nouns and the operations — with the running system derived from that.
- You
- Judge what comes back. Answer the decisions that are yours.
- Paroksh
- Models the overlay, the domain and the application, and builds — on a branch, with a live preview.
The gateA story cannot be committed until an expectation it serves is live. Work without a reason does not move.
Stage 05: Find out whether it worked
Delivered is not the same as worked. A story is validated only when a metric that measures an expectation it serves says so, with a rationale somebody wrote.
- You
- Read the evidence and make the call.
- Paroksh
- Keeps the measurements, and keeps unvalidated work visible instead of quiet.
The gateValidation needs a metric and a written rationale. "It shipped" is not a verdict.
Stage 06: Change your mind on evidence
This is where the loop closes. A belief that started as assumed becomes observed, or validated, or is superseded — and everything rooted in it is reconsidered on purpose rather than by accident.
- You
- Decide what the evidence actually changed.
- Paroksh
- Walks the graph outward from the belief you moved and names what rests on it, so nothing is quietly left behind.
The gateA superseded decision reads as superseded. Reversals stay visible; they do not evaporate.
Stage six feeds stage one. A belief that survives contact with a metric is no longer assumed, and everything rooted in it is stronger for it. That is the only sense in which this is a loop rather than a list.
Why it has to be a graph
Alignment is a shape in the graph, not a feeling about it.
The business context is a graph: personas, contexts, goals, expectations, beliefs, strategies and stories, each a node with real links to the others. That is the one structural decision the whole method rests on. If a belief were a sentence in a document you could write it in two places and never find out they had drifted. As a node, it can be pointed at — by a goal on the demand side and a strategy on the response side — and whether they converge on the same node is a fact you can query, not an impression you form in a meeting.
Unbacked
Nothing roots in this belief. You hold it, but nothing you are doing depends on it — which is worth knowing either way.
Latent
One side roots in it. A strategy grows from this belief but no goal does, or the reverse. The conviction is only half spent.
Aligned
A goal and a strategy root in the same belief. What the people you serve are reaching for, and how you have chosen to respond, grow from one conviction.
What the way refuses
A method is what it will not let you do.
Conventions are advice; a team under pressure at 4pm on a Friday ignores advice. These are not advice. Each one is enforced, and each one exists because the alternative is a question nobody can answer six months later.
A story with no reason
It must serve at least one expectation. The platform refuses to remove the last one.
Committing on an unlit promise
At least one expectation the story serves has to be live first.
Calling something validated
A metric must measure an expectation it serves, and somebody must write why.
A journey with a dead end
One entry, no dead ends, no unresolved branches — checked before it can go live.
A draft slipping into the model
Nothing is active until a person activates it.
Who holds what
Agency is never outsourced.
AI is leverage: it multiplies whatever it is pointed at. Pointed at your vision and your judgement it gives you reach you could not otherwise buy. Asked to supply the vision itself, it returns something plausible that serves no one in particular. So the split is deliberate, and it does not move.
You
- The vision, and the beliefs under it
- What you are promising, and to whom
- Which drafts become real
- Every decision the model cannot derive
Paroksh
- Drafting the model from what you say
- Turning business context into engineering context
- Building, on a branch, with a preview
- Bringing back the decisions that are yours