prabhatsharma · July 6, 2020 18:24
diff --git a/JassyWritingTest.txt b/JassyWritingTest.txt
 Prioritization test: Is preparing a great update a priority?  Have you given sufficient effort considering you are updating the CEO of one of the largest and fastest growing companies in the world?  Does your update reflect the depth and urgency with which you are building your business?

 Goal test: What is/are the goal(s) of your update? To gain feedback? Give a status update? To dive deep into a particular aspect of a project?  Try to line up your written content such that it increases the likelihood of achieving your goal(s). 

 Clear-headed test: For each sentence or bullet point, ask yourself what point you are trying to make?  State your point verbally, and if your verbal point is clearer than your written point, then change your written point. Is it possible to make your point with fewer words?

 Clarity test: Write so that that non-technical person not familiar with the games industry will understand your key points.  Does your writing require extensive industry or technical knowledge to understand?  Does your writing include undefined acronyms?

 Balance test +/-: If your reader knew what you know about your business, would they conclude that your update reflects the proper balance of relevant positive and negative information?

 Needle movers test:  Focus on the one to three issues or “needle movers” and one to two risks to call out along with the major upcoming deliverables that are worthy to raise with Andy.

 Evidence test: Is your update based in evidence?  Does your written content utilize the evidence you have to make your point?  Not all points will have evidence.  But if it is available, try to use it. 

 Insights and Actions Test: Include insights and actions we are taking as a result of the information presented.  After communicating the metrics or issues, answer “how do we feel about the results” and “what actions are we taking as a result of the information”.  Information => Insight => Action.

 Milestone test: Does your update include the status of major milestones from the previous month and upcoming milestones?  If there are any changes to previous commitments or goals (e.g. OP1 goals), they should be called out clearly. 

 Root cause analysis test: For missed deliverables, call out why we missed and the key learnings we will apply going forward.

 Path to Green test:  For Yellow and Red Goals, include steps we are taking to hit our goals.

 Risk mitigations test:  What steps are we taking to mitigate the identified risks?

 Ownership test: Write your update such that it can be copied and pasted and sent directly to Andy, without extensive editing by others.

 Half page test: Is your update a half page or less?  This test forces the writer to prioritize the most important points to share with Andy.

 Pair programming: Identify a great writer in our organization and have them review your update each month to see that it passes the tests outlined above.

 100% accuracy tests: Each statement and number made are 100% accurate.
	Prioritization test: Is preparing a great update a priority? Have you given sufficient effort considering you are updating the CEO of one of the largest and fastest growing companies in the world? Does your update reflect the depth and urgency with which you are building your business?

	Goal test: What is/are the goal(s) of your update? To gain feedback? Give a status update? To dive deep into a particular aspect of a project? Try to line up your written content such that it increases the likelihood of achieving your goal(s).

	Clear-headed test: For each sentence or bullet point, ask yourself what point you are trying to make? State your point verbally, and if your verbal point is clearer than your written point, then change your written point. Is it possible to make your point with fewer words?

	Clarity test: Write so that that non-technical person not familiar with the games industry will understand your key points. Does your writing require extensive industry or technical knowledge to understand? Does your writing include undefined acronyms?

	Balance test +/-: If your reader knew what you know about your business, would they conclude that your update reflects the proper balance of relevant positive and negative information?

	Needle movers test: Focus on the one to three issues or “needle movers” and one to two risks to call out along with the major upcoming deliverables that are worthy to raise with Andy.

	Evidence test: Is your update based in evidence? Does your written content utilize the evidence you have to make your point? Not all points will have evidence. But if it is available, try to use it.

	Insights and Actions Test: Include insights and actions we are taking as a result of the information presented. After communicating the metrics or issues, answer “how do we feel about the results” and “what actions are we taking as a result of the information”. Information => Insight => Action.

	Milestone test: Does your update include the status of major milestones from the previous month and upcoming milestones? If there are any changes to previous commitments or goals (e.g. OP1 goals), they should be called out clearly.

	Root cause analysis test: For missed deliverables, call out why we missed and the key learnings we will apply going forward.

	Path to Green test: For Yellow and Red Goals, include steps we are taking to hit our goals.

	Risk mitigations test: What steps are we taking to mitigate the identified risks?

	Ownership test: Write your update such that it can be copied and pasted and sent directly to Andy, without extensive editing by others.

	Half page test: Is your update a half page or less? This test forces the writer to prioritize the most important points to share with Andy.

	Pair programming: Identify a great writer in our organization and have them review your update each month to see that it passes the tests outlined above.

	100% accuracy tests: Each statement and number made are 100% accurate.