4 ms·
The problem with Steve Jobs advice like this is that it doesn’t work out of context. I worked for a VP and CTO who embraced this advice literally: They wanted
by Aurornis 2y ago
The problem with Steve Jobs advice like this is that it doesn’t work out of context.
I worked for a VP and CTO who embraced this advice literally: They wanted to hire smart people and have them decide what would be done. They took it to so much of an extreme that they washed their hands of the responsibility for deciding and executing anything. Their job, they thought, was to call us to meetings and then ask a lot of questions about what we were going to do.
The problems became immediately apparent when we lacked the organizational authority to actually get important things done. We could write the software, but we needed the VP and CTO to actually use their positions in meetings to get agreement from other departments about the important cross-organizational factors of getting software implemented and adopted.
Instead, it was never-ending circles of Socratic method questions: What do you need to succeed? How will your team accomplish that? Who can you talk to make that happen? Whenever we tried to make it clear that we needed them to do some work in the organization, we got a lecture about learning how to be self sufficient and get things done ourselves.
Not surprisingly, little got done. We wrote the software fine, but any time we encountered issues that required VP or C-level collaboration we hit a wall. You can only defer to IC employees to tell you what to do for so long. Beyond that point it’s just laziness.
This is also a stark contrast to how Steve Jobs actually operated, which by all accounts was extremely demanding, dismissive, and command-and-control with him at the center.
- highfrequency 2y agoGreat comment, curious to hear more about your perspective. > The problems became immediately apparent when we lacked the organizational authority to actually get important things done. We could write the software, but we needed the VP and CTO to actually use their positions in meetings to get agreement from other departments about the important cross-organizational factors of getting software implemented and adopted. Would it be fair to diagnose this as an issue where the tech side of the business ran in an open, proactive way but other departments had a top-down mentality that required interfacing with the head of your department? In other words - do you think it is a necessary/desirable feature that ICs need organizational authority from the CTO to push major changes? I get that given how the rest of the org functioned, it would have been much better to have more top-down mentality from the CTO. But is there a better equilibrium where this is not required?
- eapressoandcats 2y agoThe reality is that no matter how much you decide to push authority down, at some point there will be conflicting decisions and you need to resolve that. Most organizations lean escalation upwards eventually to the CEO to resolve disputes. If tech is trying to make changes that impact another major business area, and chaos needs to be avoided, then if you want to avoid executives being involved then members of that org need to be empowered to agree on those changes. However if you do that without structure it’s easy to just end up with organizational chaos as you wind up massively multiplying the communication channels that need to be pushed lower in the org. Someone needs to limit and direct the people responsible for those decisions if they’re not going to make them themselves.
- swalsh 2y agoThere's a few Steve Jobs quotes which have tanked the tech industry. The quote "If I'd ask customers what they wanted, they would've told me a faster horse." for example is absolutely horrible advice for 90% of companies. It implies you understand your customers business better than they do. For simple B2C businesses, that might be true. For complex B2B businesses, it's very likely not true. If your founder spent decades doing the job of his customers, and (s)he know a better way to do it using new tech, it JUST might be true. Rarely is that the case though.
- aspenmayer 2y agoI know it’s not your main point and you may already know this, but that’s usually attributed as a Henry Ford quote, not Steve Jobs. From context, you seemingly imply its Jobs’ quote, without specifically attributing it to him. But in researching this, it’s all pretty ambiguous but a decently relevant HBR article came out of it: https://web.archive.org/web/20150209203853/https://hbr.org/2011/08/henry-ford-never-said-the-fast/ https://web.archive.org/web/20150209203853/https://hbr.org/2...
- re-thc 2y ago> It implies you understand your customers business better than they do. The quote does say "I" so there is an inherent assumption there. The problem with taking any quote and "best practice" at face value that can be applied anywhere is always incorrect. > There's a few Steve Jobs quotes which have tanked the tech industry. So hence it's like the hype trains an social media driven development. People need to think. Don't blame Jobs for it.
- maayank 2y agoI like to say "you can't delegate vision"
- jiggawatts 2y agoToo true. Also, you can't delegate your own responsibility. That doesn't stop people trying.