My Destiny Inc / Website & platform case study
Programmes, resources, events and giving brought into a clearer public website.
Inside the project / An interactive reading
Website & platform case study — explore the context, material and responsibilities of this project. No invented KPIs or endorsements.
01 / 03
My Destiny Inc / The challenge
Help different audiences find a useful next step while giving the organisation a structure it can maintain.
Evidence in this chapter
The context
A growing organisation needed a coherent route through its programmes, founder information, resources, events and foundation work.
The job to do
Help different audiences find a useful next step while giving the organisation a structure it can maintain.
The approach
Organise the experience around visitor journeys, with clear programme routes, a guided pathway, a resource library and connected event and giving pages.
What the project brings together
Evidence-led outcomes
Documented change
OriginalRebuild↔Archive captures · June 2026. Screens are cropped to the same viewing frame. Current live sites may have changed.
Inspect the interface
Change by area
OriginalContent-heavy homepage with several competing routes.
RebuildA founder introduction with clear programme, resource and foundation routes.
OriginalInformation spread across the existing pages and shop.
RebuildA connected programme, resources, events and giving structure.
OriginalVisitors had to identify their own route through the content.
RebuildA guided pathway and dedicated pages for different visitor needs.
OriginalImpact material was spread across the existing site.
RebuildFoundation information brought together with giving and partnership routes.
OriginalAn external donation handoff.
RebuildA dedicated giving page explaining contributions before the handoff.
Evidence shown is the captured interface and the recorded project scope. Archive date: June 2026.
Project case study · Archive capturesAn event and community platform connecting the gathering, its speakers and booking routes.
Project case study · Archive capturesAn idea-to-plan product experience connecting coaching, guidance and practical next steps.
Scope, assumptions, dependencies and changes recorded against the brief.
User journeys, permissions, failure conditions and operating requirements reviewed before release.
Source, documentation, training and recovery responsibilities agreed as part of handover.
Start a conversation
Bring the current experience, the people it serves and the change you need to make.