Skip to content
Africa Tech FestivalMeet us in Cape Town, 17–19 Nov.

Solution

Available

Take 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.

  1. Get approval

    Which strategic goal does this serve?

    1 month
  2. Piece together the existing flows

    What is the current capability landscape?

    2 months
  3. Update outdated process maps

    How will the process run?

    2 months
  4. Consult the domain experts

    Which APIs are involved?

    3 months
  5. Map the architectural impact

    Which systems are involved, and who owns them?

    2 months
  6. Clear IT and compliance

    Which platform, and where are the blockers?

    3 months · includes waiting for a delivery slot
6 months

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

  1. Faster approval

    The change is scored against strategic goals and approved in Jira and Confluence

    1 month
  2. Existing flows already mapped

    The current capabilities and flows are in the Enterprise Twin

    2 months
  3. Process drafted for review

    Genies draft the new journey and process from the current ones

    2 months
  4. API impact found automatically

    Every API the change touches is listed; ask about any of them in plain language

    3 months
  5. Systems and owners named

    Each impacted system is listed with the person who owns it

    2 months
  6. Compliance 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

  1. Product intent
  2. Team review
  3. Aligned design
  4. 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.

  1. Impact assessment

    Assesses a proposed change against the Enterprise Twin.

    Features

    • Planned and unexpected impacts
    • Eight-section assessment
    • Readiness verdict
  2. Prioritisation

    Ranks initiatives on one rubric across the portfolio.

    Features

    • Impact, alignment, cost and time
    • Portfolio ranking
    • Selection for funding
  3. 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
  4. 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.

  1. Product intent

    Defines the feature idea, customer outcome and priority.

    Product OwnerTurns an idea into a first prototype

    Genies

    Business Analyst genieProduct Owner genie

    Requirements · User story

  2. Team review

    Genies gather context and draft questions; analysts answer and review.

    Analysts and product managersAdds domain knowledge and reviews

    Genies

    Product Owner genieExecutive genie

    Journey · Impact

  3. Aligned design

    Impacts, dependencies, architecture choices and standards are resolved together.

    Design and architectureAdds domain knowledge and reviews

    Genies

    Designer genieArchitect genie

    Visualisation · Prototype

  4. 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

    Product Owner genieArchitect genie

    Feature · Dev · Test cases

Orchestrator genie

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 conditions
  • Requirements4.1
  • Complexity2.8

Open risks2

  • Provisioning and retry ownership are incomplete.

    Complete the provisioning contract and idempotency rules.

    HIGH
  • Identity and fraud fallback paths are unproven.

    Exercise vendor failure and manual review before launch.

    MEDIUM

Capability gaps4

#Capability gapPriority
01eSIM provisioningHIGH
02Identity and KYC verificationHIGH
03Service qualificationHIGH
04Digital profileMEDIUM

Architecture decisions1

  • Use a dedicated provisioning service as the vendor boundary

    Isolate vendor contracts, retry policy and activation reconciliation from the journey layer.

    Proposed

Microservices impacted3

  • Activation API [NEW]

    HIGH
  • Entitlement Service [NEW]

    MEDIUM
  • Profile 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

    Pending
  • Resolve 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

  • Planning
  • 13 initiatives
  • Customer Churn & CX
  • Ranked by total score
Initiatives ranked by total score
InitiativeRevenueStrategic alignmentCustomer impactCostTimeTotal
Check Loyalty PointsCustomers check and redeem loyalty points in the app and in a chat channel.7.68.28.66.47.037.8
eSIM self-activationNew and existing customers activate an eSIM without visiting a store.8.17.97.85.26.135.1
Network outage notificationsProactive alerts when a customer’s area is affected.4.26.98.47.67.834.9
Prepaid bundle recommendationsPersonalised bundle offers based on usage patterns.7.96.26.67.16.834.6
Converged billing statementOne statement for mobile, fibre and value-added services.6.87.47.15.96.033.2
Fibre order trackingLive status of fibre installation orders.5.16.07.57.06.932.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

  • Initiative
  • Customer Churn & CX
  • Definition of Ready
  • 9 of 9 artefacts signed off
  • Screen design

    Signed off

    Loyalty dashboard

    Loyalty

    Points balance

    12,450

    Rewards for you

    • 1 GB data2,000 pts
    • Airtime voucher5,000 pts
    Redeem points
  • Customer journey

    Signed off

    Redeem a reward

    1. Open the app
    2. See the balance
    3. Choose a reward
    4. Confirm
    5. Get a confirmation message
  • Requirement

    Signed off

    View 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 off

    TMF658 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 off

    Balance request

    • App
    • API gateway
    • Loyalty
    • Billing
    1. App to API gatewayGET balance
    2. API gateway to LoyaltygetAccount()
    3. Loyalty to Billingusage credits
    4. Billing to Loyaltycredits
    5. Loyalty to API gatewayaccount
    6. API gateway to App200 OK
  • Data model

    Signed off

    Loyalty entities

    • Customer

      id · msisdn · segment

    • 1 : 1
    • LoyaltyAccount

      id · balance · tier

    • 1 : n
    • Reward

      id · cost · partner

  • Impact flow

    Signed off

    Systems touched

    1. Loyalty
    2. CRM
    3. Billing
    4. Loyalty engine
    5. Chat channel
  • Test cases

    Signed off

    Acceptance tests

    • TC-01Balance shows on sign-inPass
    • TC-02Expired points excludedPass
    • TC-03Redeem with low balancePass
    • TC-04Chat channel balance requestPass
  • Non-functional

    Signed off

    Requirements

    RequirementTarget
    Availability99.9%
    Response time< 800 ms
    ConsentLogged
    Peak load5k 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.