PUBLIC FEEDBACK & CHANGE LOG

You spoke.
LEAD48 changed.

This record shows how questions, critiques and early-contributor feedback have changed the LEAD48 experience, program architecture and recruitment process.

HOW THIS RECORD WORKS

Feedback should leave evidence.

01

Listen

Capture the underlying concern, not just the requested feature.

02

Decide

Accept, adapt, defer or decline it with a clear reason.

03

Change

Connect the decision to a visible page, process or program rule.

04

Report

Publish each change with the decision behind it.

Live

Published and verified on the public site.

RELEASE HISTORY

What changed, and why.

The newest improvements appear first. Each entry connects a feedback theme to the decision and public result.

RELEASE 0.12
Live

Say less, sound human and make the important words easier to read.

Feedback

The site still used too many words to explain simple ideas and some of the language felt machine-written. Important section labels and supporting text also needed to be larger.

Decision

Write as people speak: directly, warmly and with room to breathe. Keep the depth, but move it behind clear choices and deeper pages.

What changed
  • Rewrote the opening, relay, pathways, speaker and Next-Gen copy in shorter, more natural language.
  • Added a personal note from co-founders Fola Alabi and Charles Igwe.
  • Increased base, section-label, card and supporting-copy sizes across desktop and mobile.
  • Kept the detailed program architecture available in foldouts and dedicated pages.
RELEASE 0.11
Live

Make the first visit simpler, and give LEAD48 a recognizable identity.

Feedback

The site felt overstimulating. A first-time visitor might not immediately understand LEAD48, why it lasts 48 hours, what speakers contribute or what the Next-Gen Council actually does.

Decision

Turn the homepage into a doorway. Lead with purpose, progressively disclose detail and make practical value explicit.

What changed
  • Placed “Carry the baton. Build the relay. Shape the conversation.” at the centre of the opening.
  • Added a plain-language purpose statement and three-step relay explanation.
  • Rewrote the speaker question as “What leadership insight do you bring?”
  • Clarified the Next-Gen Council in one sentence.
  • Added practical session outputs, cross-regional intersections and legacy formats.
  • Introduced the LEAD48 logo, favicon and social-sharing image.
RELEASE 0.10
Live

Replace generic themes with globally grounded, region-tested questions.

Feedback

The themes were too generic. Leadership, AI and sustainability needed credible global anchors and different regional interpretations. Young people aged 13–19 also needed a meaningful role.

Decision

Use global frameworks as reference points while requiring every movement to survive contact with regional realities.

What changed
  • Established Leadership, AI and Sustainability as three program lenses.
  • Grounded eight movements in relevant UN and UNESCO frameworks without implying endorsement.
  • Added a regional test to every movement.
  • Designed a 32-member, eight-region Next-Gen Council with co-design, live challenge, co-authoring and impact-tracing responsibilities.
  • Kept the adult application restricted to people aged 18 and older.
RELEASES 0.8–0.9
Live

Make a global event feel alive without losing mobile legibility.

Feedback

The site felt too static for a global event. The first clock treatment became intrusive on mobile, while the expanded view was not useful if its regional times could not be read.

Decision

Keep the world clock interactive, but treat the mobile control as an entry point and the expanded panel as a proper reading surface.

What changed
  • Created the live LEAD48 Global Pulse with countdown, local timezone conversion, relay stops and world clocks.
  • Added interactive regional routes and baton questions.
  • Increased expanded-panel type and card sizes.
  • Reduced the mobile dock to a clear “Global time” control.
  • Removed font-blurring effects and refined responsive behaviour.
RELEASE 0.7
Live

Rebuild the 48 hours around regional working days.

Feedback

A sequence of abstract six-hour themes did not explain who was hosting when. Toronto should work a normal day and hand off to another region beginning its own morning. Europe and the Middle East also needed visible places in the plan.

Decision

Let regional working hours determine the hosting circuit while intellectual themes determine what belongs in each window.

What changed
  • Set the opening at Toronto 9:00 a.m. and the first handoff at Toronto 4:00 p.m.
  • Built an eight-shift circuit that runs twice across 48 continuous hours.
  • Added one-hour production overlaps.
  • Separated Europe, Sub-Saharan Africa, and Middle East & North Africa as collaborating desks with distinct local times.
  • Published an hourly, foldable visual schedule.
RELEASE 0.6
Live

Turn 48 sessions into one connected global conversation.

Feedback

Regional authenticity and continuity could not be left to individual speakers. The full 48 hours needed to become greater than the sum of separate sessions.

Decision

Make the handoff an intellectual and production mechanism, supported by a shared evidence record.

What changed
  • Created the Reality → Assumption → Response → Baton structure.
  • Added a live Baton Protocol and macro-handoffs between movements.
  • Designed the Global Conversation Ledger.
  • Required regional context, locally generated knowledge and unresolved tensions.
  • Designed the Global Leadership Report and annual-platform legacy from the outset.
RELEASE 0.5
Live

Make speaker selection curated, transparent and resistant to influence.

Feedback

A global speaker call needed to show applicants how decisions would be made, what quality means and how conflicts, prestige or sponsorship would be handled.

Decision

Publish the process before selection begins and separate qualification from portfolio curation.

What changed
  • Published a seven-part speaker rubric and review stages.
  • Added identity-light first review and at least two independent assessments.
  • Documented conflicts, recusals and a sponsor firewall.
  • Designed applicant-facing status visibility without exposing private notes or other applicants.
  • Clarified that title, celebrity, referral and sponsorship cannot purchase a speaking place.
RELEASES 0.2–0.4
Live

Make the opportunity, date and central question impossible to miss.

Feedback

Visitors could not easily choose a role, the call for speakers was not obvious, the event date lacked prominence and the speaker proposal did not clearly connect to the LEAD48 central question.

Decision

Give every visitor a clear path into the project and connect every speaker proposal to the global inquiry.

What changed
  • Added a six-question role finder and nested role requirements.
  • Published the call for 70 scheduled speakers plus 10 prepared standbys.
  • Made 20–22 May 2027 prominent and explained why May 21 matters.
  • Added the enduring inquiry and 2027 global provocation to the speaker page and application.
  • Added mobile navigation, back-to-top access and the Ask LEAD48 guide.
  • Built the secure recruitment administration and applicant-status surfaces.
RELEASE 0.1
Live

Create one canonical public home for LEAD48 recruitment.

Feedback

Multiple temporary links created confusion. Visitors needed one place to understand opportunities and find where they fit.

Decision

Use one canonical production site and keep detailed information within the experience instead of sending people to separate tools.

What changed
  • Established the current Netlify URL as the single public recruitment link.
  • Integrated the role finder into the site.
  • Nested detailed role requirements inside each opportunity.
  • Preserved GitHub as the source and Netlify as the production host.

THE COMMITMENT

We will not collect feedback as theatre. When a suggestion changes LEAD48, the change should be visible. When it does not, the reason should be explainable.
Return to LEAD48