Turn problems into solution - Revision history

Admin at 14:07, 17 January 2020

2020-01-17T14:07:09Z

← Older revision		Revision as of 14:07, 17 January 2020
Line 45:		Line 45:
	[[Category:HW-to-solve]]		[[Category:HW-to-solve]]
	[[Category:plan]]		[[Category:plan]]
			[[Category:Society]]

Admin at 13:34, 17 January 2020

2020-01-17T13:34:03Z

← Older revision		Revision as of 13:34, 17 January 2020
Line 1:		Line 1:
	[[~~Image~~:problem-to-solution.png\|left\|150px\|~~HW-to-solve~~]]		[[File:problem-to-solution.png\|left\|150px\|link=Turn problems into solution\|Image]]
	'''[[Turn problems into solution]]''' <small>(Plan)</small> Most of our day is spent making decisions and solving problems. Some problems we can figure out on our own, some we need help & access to resources that are outside our grasp.		'''[[Turn problems into solution]]''' <small>(Plan)</small> Most of our day is spent making decisions and solving problems. Some problems we can figure out on our own, some we need help & access to resources that are outside our grasp.

Admin at 17:58, 15 January 2020

2020-01-15T17:58:59Z

← Older revision		Revision as of 17:58, 15 January 2020
Line 1:		Line 1:
	[[Image:problem-to-solution.png\|left\|150px\|HW-to-solve]]		[[Image:problem-to-solution.png\|left\|150px\|HW-to-solve]]
	'''[[Turn problems into solution]]''' Most of our day is spent making decisions and solving problems. Some problems we can figure out on our own, some we need help & access to resources that are outside our grasp.		'''[[Turn problems into solution]]''' <small>(Plan)</small> Most of our day is spent making decisions and solving problems. Some problems we can figure out on our own, some we need help & access to resources that are outside our grasp.

	Often when we encounter a problem we think we need to discover the “why”. We need to dig and chase and determine just “why we have this problem?”		Often when we encounter a problem we think we need to discover the “why”. We need to dig and chase and determine just “why we have this problem?”
Line 41:		Line 41:

	__NOTOC____NOEDITSECTION__		__NOTOC____NOEDITSECTION__

			[[Category:HOW]]
			[[Category:HW-to-solve]]
			[[Category:plan]]

Admin at 12:52, 15 January 2020

2020-01-15T12:52:16Z

← Older revision		Revision as of 12:52, 15 January 2020
Line 39:		Line 39:

	'''Link:''' https://mikecardus.com/6-steps-to-turn-a-problem-into-a-solution		'''Link:''' https://mikecardus.com/6-steps-to-turn-a-problem-into-a-solution

			__NOTOC____NOEDITSECTION__

Admin: Created page with "HW-to-solve '''Turn problems into solution''' Most of our day is spent making decisions and solving problems. Some problems we..."

2020-01-15T12:51:10Z

Created page with "left|150px|HW-to-solve '''Turn problems into solution''' Most of our day is spent making decisions and solving problems. Some problems we..."

New page

[[Image:problem-to-solution.png|left|150px|HW-to-solve]]
'''[[Turn problems into solution]]''' Most of our day is spent making decisions and solving problems. Some problems we can figure out on our own, some we need help & access to resources that are outside our grasp.

Often when we encounter a problem we think we need to discover the “why”. We need to dig and chase and determine just “why we have this problem?”

chasing the why does not create a solution
Here are 6 steps to turn a problem into a solutions without using ‘why’

==Step 1 - Situation==
Ask How should this system operate? Or, How should the team get this done? Or, What should be happening, instead of the problem?

Framing the Situation how the work should happen is a step towards solving it. Like Russ Ackoff stated “If you cannot describe what you want to have happen with no constraints, how can you expect to have it happen with the current constraints you are dealing with!?”

==Step 2 - Observer==
Think – If someone outside this team was to see this problem solved, what would they notice? Or, If we were doing what we should how would I see the team reacting? Or, If this problem is suddenly solved how will I notice that it is working?

Taking with Observer mindset will get you out of your own head a little shifting your perceptions to find steps that may move the solution closer.

==Step 3 - Level==
Determine on a scale from 0 – 10 with 10 being that things are working exactly as they should, 0 being the opposite; where are you now?

Leveling your solution into a measurement will allow you to have some friction to grab pulling the solution closer.

==Step 4 - Validation==
What is already working well enough to keep you where you are on that scale?

Validating examining what is working well already and how you are able to keep that number as high as it is, might point to some ideas of what-to-do.

==Step 5 - Exception==
Is there a place, time, location, something somewhere where your solution has happened or is already happening; even just a little bit?

Seeking Exceptions breaks the psychological inertia of ‘always the same damn thing’ to …it is already happening over there and we can make that happen here.

==Step 6 - Decision & Direction==
Based upon what you know/think what is your first small step to solve this?

It is time for Decisions & Direction choosing 1 small step will create progress and allow you to test to find what works and how to do more of that.
There it is 6 steps to turn a problem into a solution.

'''Link:''' https://mikecardus.com/6-steps-to-turn-a-problem-into-a-solution