Project method: Difference between revisions

From The Jolly Contrarian
Jump to navigation Jump to search
Created page with "{{a|project|}}To formulate a project: ===State the problem=== What is the testable question or problem you are trying to solve. For example: how to make the process of rev..."
 
No edit summary
Line 1: Line 1:
{{a|project|}}To formulate a project:
{{a|projects|}}To formulate a project:
===State the [[problem]]===
===State the [[problem]]===
What is the testable question or problem you are trying to solve. For example: how to make the process of reviewing a confi more effective.
What is the testable question or problem you are trying to solve. For example: how to make the process of reviewing a confi more effective.

Revision as of 16:49, 29 December 2020

The Devil’s Advocate™ — projects you can try at home
Click ᐅ to expand:
Tell me more
Sign up for our newsletter — or just get in touch: for ½ a weekly 🍺 you get to consult JC. Ask about it here.

To formulate a project:

State the problem

What is the testable question or problem you are trying to solve. For example: how to make the process of reviewing a confi more effective.

Research and analysis

Problem-solve it: what is the problem? What is the ideal end goal? Before going into solutionising mode, go through this process thoroughly. Don’t assume a given tool is the answer: it may be, but go through the critical phases of the process to identify whether fixing this particular aspect will make a difference. For example, if doc generation takes about 45 minutes of a three month negotiation process during which the negotiator spends 10-5 hours chasing various stakeholders inside the organisation for comments, escalations and responses, then document assembly probably isn’t the solution you are looking for.

Formulate solution

Once you have done that, formulate a proposed solution and some measurable success/failure criteria. Say you were using the Molesworth self-adjusting thank-you letter