Quality Requirements
Verified ResearchOS for logic and coverage of client objectives, then routed project appropriately.
- It is important here that we use ResearchOS to reduce scope. The only time we would attach a ResearchOS run that is not verified and used to reduce scope would be if the client emailed in and we didn’t verify it due to turnaround time.
- Remember, we don’t only have access to the standard ResearchOS output. We also have access to 10-K tools, the ability to clarify a competitive landscape, and the ability to determine competitors for us! See more here.
Addressed the complete client chat, including client comments.
The client's goals and objectives are clearly stated.
- Self-explanatory
- We never copy/paste directly from the chat. Read the chat and convert it to the normal Wonder jargon.
The project is feasible as presented.
No primary research (unless approved), dependencies & clarifications are addressed if needed. If technology is used to reduce scope, it is vetted before going to the analyst.
- Again, it is self-explanatory, but make sure that if you put something out there, it is actually doable.
The project is scoped accurately based on scoping guidelines or ResearchOS output.
Research Criteria are concise and clearly explained.