Diagnosis module: Difference between revisions

← Older edit

Diagnosis module (view source)

Revision as of 13:09, 4 October 2021

623 bytes added , 4 October 2021

no edit summary

Amwelladmin

Bureaucrats, Interface administrators, Administrators

82,503

edits

@@ Line 1: / Line 1: @@
 {{a|gsv|}}Scratch pad on how to do the initial scoping of a process/documentation fix:
-First thing you need is [[symptom]]s. What is wrong? Why is someone calling you?
+First thing you need is to identify the [[symptom]]s. What is wrong? Why is someone calling you?  Symptoms are usually the things you want to fix — but they are not the causes of the problem. They are its output; its ''manifestation''. If you address symptoms without addressing their [[root cause]], they will continue to recur as soon as you stop doing what you are doing.
-===Describe existing process===
+===Describe existing symptomatic process===
 Understand how and why we got here in the first place.
-#Map out the ''symptomatic'' process that the client currently goes through that generate the symptoms.
+====Map out how the ''symptomatic'' process currently happens. ====
-a.	What outcomes do the business want to achieve?
+*What is the desired outcome?
-b.	What are the legal/disclosure risks the current legal docs/disclaimers are addressing?
+*What is typical path, including [[horizontal escalation]]s and expected hand-offs?
-c.	How effective are they?
+*What risks and unwanted outcomes are addressed and how are they addressed?
-(iii)	What are the practical challenges/delays/inefficiencies in this process.
+:*Are they the right things to focus on?
-a.	What can go wrong?
+:*How effectively are they dealt with? (is it “day-to-day relationship management”, “enforceable legal remedies” or disclaimers and “disclosures”) ie are these effective [[coping strategies]]?
-b.	What unnecessary hand-offs and horizontal escalations are there?
+====What are the practical challenges/delays/inefficiencies in this process@ ====
-(iv)	In a perfect world, what would be the optimal process? (ie ignoring tech/budgetary constraints)
+*What can go wrong?
-a.	What would have to change to make that perfect world
+*What unnecessary hand-offs and [[Horizontal escalation|horizontal escalations]] are there?
-i.	Things that are practically impossible
+====Theoretical solutionising====
-ii.	Things that are too expensive
+In a perfect world, what would be the optimal process? (ie ignoring tech/budgetary constraints)
-iii.	Things that involve changes to policies and rules
+*What would have to change to make that perfect world
-iv.	Things you could change now.
+*Things that are practically impossible
-(v)	Assuming that perfect word is unattainable, what would be the nearest practical scenario we could realistically get to?
+*Things that are too expensive
-i.	What dependences/challenges/changes would we have to make to get there (e.g.: challenging the rule that we have to send out the “legal entity disclosure”; a decent file management system, harmonising us rules etc)
+*Things that involve changes to policies and rules
-ii.	Who would need to agree to it?
+*Things you could change now.
-iii.	What would need to be done and who would be doing it?
+====Practical solutionising====
-iv.	How would you implement it?
+Assuming that perfect word is unattainable, what would be the nearest practical scenario we could realistically get to?
+*What dependences/challenges/changes would we have to make to get there (e.g.: challenging the rule that we have to send out the “legal entity disclosure”; a decent file management system, harmonising us rules etc)
+*Who would need to agree to it?
+*What would need to be done and who would be doing it?
+*How would you implement it?
+{{sa}}
+*[[Coping strategy]]