01 / Product as Code
One rate change.
A bigger story.
A banking product is a set of promises. Make those promises explicit enough for people and software to explore together.
PRODUCT LAB / INTERACTIVE ILLUSTRATIONBased on SAV-FIXED
savings-fixed.json ILLUSTRATIVE SUMMARY
{
"productCode": "SAV-FIXED",
"currency": "EUR",
"baseRate": 0.0250,
"bonusRate": 0.0100,
"conditions": [
"no withdrawals in 30 days",
"balance at least EUR 1000"
]
}
A readable summary of the sample definition. Explore the source for its complete structure and rules.
FROM DEFINITION TO OUTCOME
Change a number.
Change a number.
See what it means.
ILLUSTRATIVE ANNUAL GROSS INTEREST
€350.00
Base €250.00Bonus €100.00
Simple annual illustration on €10,000. Constant balance and conditions. Before fees, tax and compounding.Read the real definition ↗
The next connection
The number is the start.
The review is the story.
A concept for bringing product simulation, checks and human approval into one shared change journey.
PROPOSED PRODUCT CHANGE JOURNEY
01 / DEFINITION
Propose.
Make the new terms explicit.
02 / SCENARIOS
Simulate.
Explore eligible and ineligible cases.
03 / EVIDENCE
Compare.
Bring results into the review.
04 / DECISION
Review.
A person examines the proposal.
The proposed rate starts in a versioned definition.A shared language for product teams and developers.
For the banker.
Explore the terms, the conditions and the customer outcome in one place. Ask better questions before a change reaches a customer.
For the builder.
Start with typed definitions and an interpreter. Connect the same product rules to simulations, tests and review.
Explore the Product as Code architecture ↗Every product change raises another question: what is the evidence?
Explore controls & evidence →