Solution
AvailableTake a change from idea to ready to build.
Digital Practitioner assesses what a change touches, then genies draft every artefact the team needs to start building. When the owners sign off, the change meets its Definition of Ready.
- Solves
- Changes that take months of discovery before build
- Used by
- Product owners, analysts, architects and delivery leads
- You receive
- An impact assessment, a priority score and nine delivery artefacts
- Proof
- Telco pilot: a digital checkout taken to Definition of Ready in days, against an estimate of months
The problem
Six months before build starts.
A digital change takes about six months of research across 20 teams before anyone can start building.
ExampleA telco wants more customers to sign up on its website instead of through a sales agent. Before anyone builds, every team maps its own domain to find out what already exists.
Get approval
Which strategic goal does this serve?
1 monthPiece together the existing flows
What is the current capability landscape?
2 monthsUpdate outdated process maps
How will the process run?
2 monthsConsult the domain experts
Which APIs are involved?
3 monthsMap the architectural impact
Which systems are involved, and who owns them?
2 monthsClear IT and compliance
Which platform, and where are the blockers?
3 months · includes waiting for a delivery slot
20 teams and hundreds of meetings, just to learn whether one change can be built
How it works
Six months of discovery, down to days.
The same six questions, each answered from the Enterprise Twin.
Illustrative
Faster approval
The change is scored against strategic goals and approved in Jira and Confluence
1 monthExisting flows already mapped
The current capabilities and flows are in the Enterprise Twin
2 monthsProcess drafted for review
Genies draft the new journey and process from the current ones
2 monthsAPI impact found automatically
Every API the change touches is listed; ask about any of them in plain language
3 monthsSystems and owners named
Each impacted system is listed with the person who owns it
2 monthsCompliance checked as work moves
Each change is checked against its standard and approved by a named person
3 months · includes waiting for a delivery slot
Each question answered in days
- Product intent
- Team review
- Aligned design
- Definition of Ready
Modules
Four modules, from impact assessment to delivery tracking.
Genies draft the work in each module, and its owner signs it off before the change moves on.
Impact assessment
Assesses a proposed change against the Enterprise Twin.
Features
- Planned and unexpected impacts
- Eight-section assessment
- Readiness verdict
Prioritisation
Ranks initiatives on one rubric across the portfolio.
Features
- Impact, alignment, cost and time
- Portfolio ranking
- Selection for funding
Definition of Ready
Genies draft the artefacts each discipline needs, and owners sign off.
Features
- Nine artefacts in one run
- Sign-off progress
- Stakeholder approvals
Delivery tracking
Tracks each initiative to completion and writes the outcome back to the model.
Features
- Programme pipeline
- Jira and Confluence integration
- Shipped work compared with the first draft
Genies
Genies do the work, people decide.
Genies draft each artefact from the Enterprise Twin, the Orchestrator coordinates them, and each owner approves their part.
Product intent
Defines the feature idea, customer outcome and priority.
Product OwnerTurns an idea into a first prototype
Genies


Requirements · User story
Team review
Genies gather context and draft questions; analysts answer and review.
Analysts and product managersAdds domain knowledge and reviews
Genies


Journey · Impact
Aligned design
Impacts, dependencies, architecture choices and standards are resolved together.
Design and architectureAdds domain knowledge and reviews
Genies


Visualisation · Prototype
Definition of Ready
Small features can be ready in hours, larger ones in days.
Delivery teamPicks up the signed-off artefacts and starting code
Genies


Feature · Dev · Test cases

Orchestrator
Assigns each task to the right genie and coordinates the work between them, from one step to the next.
Then
Ship, learn and update
Ship in days
Deliver the change with the full context attached.
Learn from every release
EcoGenie compares what shipped with its first draft.
Update the Enterprise Twin
Every team works from what actually shipped.
Each shipped change is written back to the Enterprise Twin.
You receive
Impact assessment: everything a team needs to start building.
Each initiative includes an eight-section impact assessment, a priority score and nine delivery artefacts.
Illustrative
Readiness verdict
3.3/5
Proceed with conditionsOpen risks2
- HIGH
Provisioning and retry ownership are incomplete.
Complete the provisioning contract and idempotency rules.
- MEDIUM
Identity and fraud fallback paths are unproven.
Exercise vendor failure and manual review before launch.
Capability gaps4
| # | Capability gap | Priority |
|---|---|---|
| 01 | eSIM provisioning | HIGH |
| 02 | Identity and KYC verification | HIGH |
| 03 | Service qualification | HIGH |
| 04 | Digital profile | MEDIUM |
Architecture decisions1
- Proposed
Use a dedicated provisioning service as the vendor boundary
Isolate vendor contracts, retry policy and activation reconciliation from the journey layer.
Microservices impacted3
Activation API [NEW]
HIGHEntitlement Service [NEW]
MEDIUMProfile Vault [NEW]
MEDIUM
Features
13across 6 journey phases
- Approved 8
- In review 2
- Needs work 3
SWOT
Strengths 4
Customer-centric coverage across the journey
Weaknesses 4
No provisioning back-end specifics
Opportunities 3
A reusable orchestration layer
Threats 3
Inconsistent reason codes
Conditions to proceed2
Close the high-priority capability gaps before build
PendingResolve qualification gaps before build
Pending
Prioritisation
Rank every initiative on the same scorecard.
Each initiative is scored against business goals, and the team records why.
Illustrative
| Initiative | Revenue | Strategic alignment | Customer impact | Cost | Time | Total |
|---|---|---|---|---|---|---|
| Check Loyalty PointsCustomers check and redeem loyalty points in the app and in a chat channel. | 7.6 | 8.2 | 8.6 | 6.4 | 7.0 | 37.8 |
| eSIM self-activationNew and existing customers activate an eSIM without visiting a store. | 8.1 | 7.9 | 7.8 | 5.2 | 6.1 | 35.1 |
| Network outage notificationsProactive alerts when a customer’s area is affected. | 4.2 | 6.9 | 8.4 | 7.6 | 7.8 | 34.9 |
| Prepaid bundle recommendationsPersonalised bundle offers based on usage patterns. | 7.9 | 6.2 | 6.6 | 7.1 | 6.8 | 34.6 |
| Converged billing statementOne statement for mobile, fibre and value-added services. | 6.8 | 7.4 | 7.1 | 5.9 | 6.0 | 33.2 |
| Fibre order trackingLive status of fibre installation orders. | 5.1 | 6.0 | 7.5 | 7.0 | 6.9 | 32.5 |
Definition of Ready
Definition of Ready artefacts.
Every artefact a telco needs to start building, generated by genies and signed off by their owners.
Illustrative
Check Loyalty Points
Screen design
Signed offLoyalty dashboard
Loyalty
Points balance
12,450
Rewards for you
- 1 GB data2,000 pts
- Airtime voucher5,000 pts
Customer journey
Signed offRedeem a reward
- Open the app
- See the balance
- Choose a reward
- Confirm
- Get a confirmation message
Requirement
Signed offView loyalty balance
As a prepaid customer, I want to see my loyalty balance in the app, so that I can redeem rewards before they expire.
- Given
- a signed-in customer with points
- When
- they open Loyalty
- Then
- the balance shows within 2 seconds
- And
- expiring points are flagged
API specification
Signed offTMF658 loyalty account
GET
/tmf-api/ loyaltyManagement/ v4/ loyaltyAccount/ {id} { "id": "LA-204918", "status": "active", "balance": { "amount": 12450, "units": "points" }, "expiringPoints": [{ "amount": 900, "date": "2026-12-31" }], "relatedParty": [{ "role": "customer", "id": "C-88213" }] }Sequence diagram
Signed offBalance request
- App
- API gateway
- Loyalty
- Billing
Data model
Signed offLoyalty entities
Customer
id · msisdn · segment
- 1 : 1
LoyaltyAccount
id · balance · tier
- 1 : n
Reward
id · cost · partner
Impact flow
Signed offSystems touched
- Loyalty
- CRM
- Billing
- Loyalty engine
- Chat channel
Test cases
Signed offAcceptance tests
- TC-01Balance shows on sign-inPass
- TC-02Expired points excludedPass
- TC-03Redeem with low balancePass
- TC-04Chat channel balance requestPass
Non-functional
Signed offRequirements
Requirement Target Availability 99.9% Response time < 800 ms Consent Logged Peak load 5k req/s
Every work item is tracked from generation to sign-off, across initiatives and teams.
See EcoGenie on your own architecture.
Bring a change you’re planning. We’ll show you how the genies assess it, and who signs it off.