2 ms·
I'd make a little alarm sound when there are reconciliation issues between different perspectives, so I don't end up wasting effort until I can de-contextualize
by themodelplumber 6y ago
I'd make a little alarm sound when there are reconciliation issues between different perspectives, so I don't end up wasting effort until I can de-contextualize and identify which perspectives need attention.
For example, if I'm at a point in a project where I need to get a task done:
- The checklist perspective: "Task A must be done."
- But then there's the logical perspective: "How must it be done? There was a recent discussion that affects the process."
- And then there's the time-intuition perspective: "Something is wrong, the discussion included aspects that may alter the way the project is fundamentally designed. If we continue down this path we won't be able to complete the project without a change in approach."
- And then there's the feeling/emotive perspective: "I really hate the way this project keeps changing. It's only fair that we discuss this. Better to discuss it now than later."
- And finally, the checklist calls: "You need a new list for all that new stuff, right? What's the status in making that?"
And these are only _some_ of the perspectives that can complicate things!
Still, it's really helpful to attend to this kind of perspective-integration. Without it, even one outstanding reconciliation can bring things to a sort of inscrutable halt, and _that_ tends to look and feel like unreasonable procrastination.
Plus if anybody mentions the delay, it's easier to make a quick single- or double-perspective decision than to reconcile things in multiple dimensions, which tends to compound the issue but also informs a superior process.
I have some templates I use to work through these kinds of situations, but I'd much rather outsource the alert itself to some external system that doesn't require so much consciousness...