In an ideal world, we would

[kexej28769@nongnue]

A promotion schedule. So that means we actually know what we're doing and in what order as we launch. It could be before launch that we're doing a lot of things around private beta or around collaboration with some of these influential people and publications. Or we haven't defined the audience yet. We need to do that. We have that schedule and work items by each team member, and we need a rollback plan. So if at any point along the way, the person who owns the product process says, "This isn't good enough," or, "We have a fundamental flaw," or, "This flamethrower we're building is shooting ice instead of fire," we should probably either rename it and rebrand it or roll it back. We have that structure in place.

☑ Frequently asked questions from the austria number data /test period, both from potential customers and influencers


Next, frequently asked questions. This is where the beta or test period and the test users are very useful, because they will have asked us a lot of questions. They will have asked whether they are playing with the product or observing or using it. We should be able to take all of these questions from both potential customers and influencers, and we should have those answers compiled for our customer service and support teams and for those who are intervening with the press and reaching out to influencers.

A also publish them online. We would have a place where we could reference them. They have already been published. This is especially useful when the press and influencers are covering a launch and they are linked to a, "Oh, here's how the snow thrower is," I'm assuming, "that we're building to work, and here's what temperature it's safe to work at," etc.

☑ Media assets and content for press/influencer use