Pilots and High Priority projects are very similar to normal QA checks. Please remember the following:

• QA check as normal, making sure of robustness, grammar, alignment (in SS and presentations), proper links, RCs, etc. beautiful presentations, etc. be detailed, please (as possible within the time allowed).

Also, check that:

There are NO flying bullet points before the image. (change the image format so it is not in bullet points).

• Make sure that the Image source is not listed as a title in the table of content. If there is one, there called “Source,” change the format of the image so it is not recognized as a title and it goes away.
• Go to the strategy > Look for the Slack Thread linked (in the comments) and reply in there, tagging the CSM to let them know that the portion has been completed and QA checked. If needed (e.g., there were important corrections but not enough to launch a full revision), provide feedback about the analyst and changes you made there and let Lisa know about the quality side.
• Do NOT send it to the client. New Logo projects are sent by CSM once all parts are done. So just notify in the thread that the QA check is done, tagging @james, and he will take care of it.

• New Logo are the accounts that have signed a small credit to test us (we want to impress them to win the full contract).
• Pre-pilot are those we haven’t signed yet. Often time, Pre-pilot clients don’t have a Wonder UN ready, those will come under James’ Toha account, and he’ll indicate that the strategy is for a potential new client.
• Sometimes these pre-pilot UNs are actually part of a team or a POC between Wonder and the real decision-maker; the reason why the proposals need to be collaborative (hence the need for a GDoc) is so they can share the outline with their team and decide to buy the project and/or for other team members/decision-maker to add comments to the proposal We want them to have access to collaborate and give comments about the outlines.

✈ 1st Strategy:

1. We take the project and add the :slack: Slack thread to the comments as shown in the template. In the Slack thread, we let CSM know we are handling it. The Slack thread is the Trello post from the #project-management-speed channel. See the example here.
2. Prepare the outline as usual on the strategy dash.
3. Explain any data availability issue well.
4. Break the PRs as they will be submitted from the start. For example, if you will submit 9 hours per company for 10 companies, do the 10 PRs per company and don’t keep them all in a single 90 hours PR. This will allow the client to see the exact QA hours that will be charged, as they may change when split.
5. If it is a competitive landscape for pre-pilots, they prefer to launch them in waves to ensure we nail the companies of interest. We usually identify them and send them back to get feedback. Then we decide if we will redo wave 1 to get a better list or if we proceed with the companies they liked in the full analysis. So split the project into PRs for identification (first wave) and PRs for analysis (second wave) to keep the QA hours correct. Explain this to the client as Research Manager Notes under the Data Availability portion. Example: “Research Manager Note: This portion will be launched first to identify the companies; once the companies have been delivered and confirmed to match the criteria, the next portion will be launched to complete the analysis. The scope for the second portion will be adjusted based on the number of companies selected.”
6. Use the New Logo comments template (see here).