Discovery spike Retiring MI · Member Intelligence
Retiring Doclets, keeping the use cases.
Four workstreams that turn a risky legacy platform into a clean sunset.
ANGLE 1
Survey the usage
Ask every associate how Doclets actually fit their workflow today — who creates, who sends, what matters.
ANGLE 2
Size the gap
Map survey results against what we have. Hypothesis: an update to sharing in MI-6 closes it.
ANGLE 3
Migration strategy
Engineering assesses the feasibility of moving existing doclets into our documents backend.
ANGLE 4
The URL question
Thousands of doclet links live in inboxes. Redirect them, or sunset them gracefully — decide, don't break.
Click through to see how the four fit together. →
The Situation
A legacy platform with open doors.
MI (Member Intelligence) lets associates spin up custom content sites — Doclets — on unprotected URLs and send them to anyone. Published doclets also surface inside the member app through what is essentially an iframe. It works, but it costs real money to keep alive and every link is a door with no lock.
🛠️
Associate builds a doclet
Custom content site assembled in MI.
🔗
Unprotected URL
Anyone with the link can open it. No login, no expiry.
no auth
📱
Iframed into the member app
Published doclets render inside the app experience.
0
Doclets created
0
Published to the app
2
Reasons to retire: cost + security
The constraint: we can't just switch it off. Half of these doclets are live in the member app, and associates have built real workflows on top of them. Retirement has to be an upgrade, not an amputation.
Angle 1 · Understand Usage
First, ask. Every associate, five minutes.
A short survey to every department that touches Doclets. Not "do you like them" — how do they fit your workflow, which ones actually matter, and what breaks if they disappear.
World 50 Doclets Usage Survey
As we look to retire Doclets, tell us what the new solution needs to account for.
How often do you create or send Doclets?
DailyWeeklyMonthlyQuarterly or less
If we move to a new system, how important is it that your published doclets are recreated there?
Not at all critical Absolutely critical
If Doclets were no longer available, what would be your biggest concern?
~6
Questions · under 5 minutes
Going to
ContentMember ExperienceMembership DevMember ServicesProduct
Respondents link the doclets they actually rely on — turning "2,000 published" into a ranked list of what really has to survive.
Angle 2 · Size the Gap
The gap between today and "good enough to switch."
Survey results tell us which use cases have to persist — huddle-call replays, engage-call content, team write-ups, low-friction sharing with executives who won't fill out forms. We map those against what MI-6 does today. The hypothesis: the gap is a sharing feature, not a new platform.
MI-6 has today
✓Content authoring & templates
✓Publish to the member app
✓Documents backend
✓Member auth & identity
The gap
Use cases need
＋Share sites without publishing to the app
＋Low-friction external access
＋Optional guarding: password / email match
＋Presentation-friendly frames & preview
The bet: update sharing in MI-6 — one feature, already mocked up — and every surviving doclet use case has a home on a platform we already run. No new system to buy, build, or secure. The survey validates (or corrects) this before we commit.
Angle 2 · The Mock, Working
MI-6 sharing: try the flow.
Publish to the app, keep a share site, or both — with three levels of guarding. Change settings on the left; the visitor's view updates live.
Author view · MI-6 share settings
Huddle Call Replay — Q3 Supply Chain
Doclet-style content · owned by Member Experience
Publish to Member AppContent also appears in the app — independent of the share site.
Share site accessWho can open the share link?
mi6.world50.com/s/hx92k4
Visitor view · live preview📱 also in Member App
World 50 Group
Huddle Call Replay — Q3 Supply Chain
Enter your email to view. That's it — no form, no account.
Huddle Call Replay — Q3 Supply Chain
Shared by World 50 Group · Member Experience
✓ access logged
Still open from the mock: topic search / feed view · subpages with nav · preview share-view vs. app-view · created-by & last-updated · bulk-upload invite emails. The survey decides which earn a place in v1.
Angle 3 · Migration Strategy
Can 2,000 published doclets move on their own?
"Is it feasible to migrate existing doclets into the documents backend?"
📄
Doclet in MI
Legacy custom site — pages, embeds, links, uploaded files.
➜
🔬
Engineering spike
Inventory the content shapes. What parses cleanly, what doesn't?
➜
🗄️
Documents backend
Existing store behind MI-6 — the target for anything worth keeping.
➜
📱
Rendered natively
No more iframe — surviving content renders like everything else.
🟢 Bulk-migrate
If content parses cleanly, script the move for everything still in use.
🔵 Assisted rebuild
If it doesn't, hand-migrate only the doclets the survey flags as critical.
🟡 Archive the rest
Snapshot and retire the long tail — recoverable, not maintained.
Why the spike matters: the answer decides the whole cost curve. Clean migration means the survey's "recreate my doclets" question is nearly free to satisfy. Messy migration means the survey's ranked list decides where human effort goes.
Angle 4 · The URL Question
The links are already in the wild.
Every doclet URL ever sent still sits in an inbox somewhere — members', prospects', executives' teams'. When MI goes dark, each of those links needs a deliberate answer, not a 404.
mi.world50.com/doclet/8kx31…
↪️ Forward to the new home
Doclet was migrated → the old URL redirects to the corresponding content in the new system. Seamless for the member; the link they saved keeps working.
🌅 Graceful sunset page
Doclet was retired → a branded page: "this content is no longer available," with a pointer to where to go or who to ask. Honest, on-brand, no dead ends.
Per-doclet, not platform-wide: the migration outcome (Angle 3) decides which path each URL takes. Redirect what moved, sunset what didn't — and keep the redirect layer alive long after MI itself is gone.
The Sequence
Four angles, one clean sunset.
📋
Survey
Who uses Doclets, for what, and which ones matter.
📐
Gap → MI-6 sharing
Build the sharing update that gives every use case a home.
🚚
Migrate / rebuild / archive
Move content per the feasibility spike and the survey's ranked list.
🔗
URL cutover
Redirect what moved, sunset what didn't. Then MI goes dark.
4
Workstreams
0
Published doclets accounted for
1
Platform we already run
0
Unprotected URLs left behind
Doclets retire. The use cases don't.
Lower cost, real access control, one platform — and nobody's saved link ever hits a dead end.