4 ms·
Generally, this technique can work for adding any kind of pet tech to your work stack: - identify an isolated, low-risk need. - develop a solution in your tec
by JoelMcCracken 7y ago
Generally, this technique can work for adding any kind of pet tech to your work stack:
- identify an isolated, low-risk need.
- develop a solution in your tech (usually on your own time).
- introduce to your boss/company as already developed.
The biggest risk for the business is needing to replace the component. In these cases usually an isolated, irregular solution is acceptable
- yowlingcat 7y agoWhy the phrase "pet tech"? This is a good way to "ask for forgiveness, not permission" which I approve of. But is the goal of adding "pet tech" necessarily a good one? If technology is actually going to move your firm forward long term and is a good long term decision, it's not pet technology. It's a good decision, and it's something that hopefully your team and firm is behind.
- marcinzm 7y agoIf it's a good decision then you shouldn't have to ask for forgiveness rather than permission. It's also, if it's not just a pet technology, a strategic decision that impacts everyone on your team and it's pure ego to think you should make that decision alone.
- yowlingcat 7y agoI agree with both points. I do think there are orgs where, due to shall we say "personality constraints" you can have majority consensus that a decision is good and should be made but it can still get roadblocked. Of course, such situations are an indicator of a dysfunctional org; in a functional one, you have these kinds of open discussions and like you said, you don't need to ask for forgiveness rather than permission, and you can make these strategic decisions together as a team.