Identifying and understanding feedback loops is key.
Building systems that actually solve problems and produce the results you intend isn’t an instinct thing.
What information are you paying attention to?
What reactions result from this information?
Do these reaction solve the problem?
What secondary effects do these reactions have?
When different people fail similarly across a system, it’s likely the system itself, not the people, at fault.
People not following your systems?
Build systems people will follow.
The over all goal of each persons work must be shared.
It never ceases to amaze me how quickly people in different parts of a system can begin both working at odds with each other and the purpose the system was setup to achieve.
@RovingVrain@weareshepherd I’ve been working through this problem as well.
I don’t think people mind working alone, it’s isolation that seems to throw them off.
As long as employees know they can get support when needed, they’ll tend to thrive.
*good employees will thrive
Prioritize HOW something gets done over WHAT gets done.
Tasks lacking deliberate solutions will lead to double handling and inconsistent results.
Time and resource requirements become unpredictable and so do the outcomes of WHAT gets done.
And anyway, your plan is not perfect.
The real problems you face during implementation will always be more informative than the problems you can recall or imagine
@SamMatla Exactly, even if you did intellectually figure out the ideal, it wouldn't get you all that much closer to achieving it. Better to discover ideals in real action taken.
Before anything, know how it’s structured.
Inputs - Data, information, and resources
Sytems - Organisation and transformation of Inputs
Outputs - The result of a Systems design