I'd love some advice on timing a v1.0 roll-out for our "build in public" platform.
We currently have 4,192 registered, active folk on our news platform, OneSub and on Monday we're planning to move a big update from beta to live.
Of those 4k registered users;
.. which means;
We have ~40 people using the new version of the app already under our "Beta" programme...
When Monday comes, we know that it's not the end of a build cycle (despite 12 months of back-end modelling, engineering and sweat)... it's actually the start of a UX, PMF, comms build cycle because as soon as people start using it we'll discover all the things we've mis-assumed, forgotten, missed etc! 😆
So how should we communicate the "New Version" .. how much fanfare? How do we set expectations (it's maybe, visually, not changed that much but the personalisation/sub-editing/comprehension systems have been totally overhauled)... Do we go in all guns blazing: "Wooo, look, all new, tada!" ... do we do it quietly and see what engagement is like before touching the 90%?
Should we communicate out in small batches, 250 people at a time... leave them a week or two... make improvements... then next 250... make Eric Ries proud?
Has anyone else been in this situation? New day, new version, maybe a pivot (we've not pivoted, we've just had signups long before we had a sticky product) ... and succeeding in re-onboarding a load of stale users.
We have a degree of onboarding/coaching/gamification mechanics under the hood (and Intercom, until we slip out of the early-stage discount in March and can't afford it anymore 😭)... so we can onboard people quite slickly...
I feel I have "one shot" at re-engaging these folk...
... and 3,900 target-audience people would be expensive to find anywhere else!
I do not want to muck this up.
Help please 🙏