Post History
You can cast it as an early report on your beta launch, or as a preview of your forthcoming launch. Assuming that you're restricting it now so you can work the kinks out before spreading more wide...
Answer
#3: Attribution notice added
by
System
·
2019-12-08T05:19:03Z (over 4 years ago)
Source: https://writers.stackexchange.com/a/23417 License name: CC BY-SA 3.0 License URL: https://creativecommons.org/licenses/by-sa/3.0/
#2: Initial revision
You can cast it as an early report on your _beta launch_, or as a preview of your _forthcoming launch_. Assuming that you're restricting it now so you can work the kinks out before spreading more widely, it helps to also talk about what you've learned -- we found and fixed this performance problem at scale, we discovered that this one part of our user interface was confusing and did such-and-such to fix it, this week we fixed this many user-reported bugs (average turnaround time N hours), and so on. Along with conveying news about your feature, for a beta launch like this you want to convey that there is _forward motion_ -- that people who have to wait are benefiting from this wait. Assuming that the broader availability is in the foreseeable future, regular progress reports can also help you keep people interested -- this is the "update bulletin" model used by Kickstarter and similar services.
#1: Imported from external source
by
System
·
2016-06-18T00:21:33Z (almost 8 years ago)
Original score: 2