3 ms·
In a technical environment the first step is probably to write your ideas down. Sleep on it, review, and then share with a few people you trust for candid feedb
by skmurphy 10mo ago
In a technical environment the first step is probably to write your ideas down. Sleep on it, review, and then share with a few people you trust for candid feedback. From there you can share more widely, fine tune and adjust, or realize that you mis-assessed.
- raw_anon_1111 10mo agoIt’s called “pre-wiring” https://medium.com/@unwrittenbusinessguide/pre-wiring-the-art-of-getting-stakeholder-buy-in-c9bf11fcea46 https://medium.com/@unwrittenbusinessguide/pre-wiring-the-ar... https://www.manager-tools.com/2007/11/how-to-prewire-a-meeting https://www.manager-tools.com/2007/11/how-to-prewire-a-meeti... https://candidcio.com/2008/05/09/the-value-of-the-pre-wire/ https://candidcio.com/2008/05/09/the-value-of-the-pre-wire/
- skmurphy 10mo agoI think in the early stages, the intent is self-rescue: prevent yourself from going off half-cocked. I see it as a way to gather feedback from trusted peers who have knowledge of the problem area. If it proves out, then they can help you sell it, but my primary intent was to encourage a "measure twice, cut once" approach instead of running with an idea without adequate preparation. If you cannot find at least three things that might go wrong with your approach, you probably have not thought it through. The intermediate step between soliciting feedback and "pre-wiring" is a pre-mortem, where you actively solicit potential failure modes and stumbling blocks.