|
|
| | Ask HN: How does Apple achieve both secrecy and quality for a release? | | 99 points by billti on April 18, 2022 | hide | past | favorite | 87 comments | | I know there are several counterexamples, but in general I'm impressed that Apple manages to keep new products/features under wraps until a major event, and then the product is in stores a couple weeks later with pretty high quality (user experience, reliability, minimal major bugs, etc.) Can anyone who has first-hand knowledge shed some light on how this is achieved with what I assume is quite limited user testing to contain leaks. Even working on products with multiple public betas and customer feedback sessions, it's hard to hit a high quality bar with a product release. |
|

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact
|
- Secrecy does actually get in the way. It's not great when you aren't aware of large features or products that will impact your work.
- Apple hires people who have great product design instincts, and even end-users know Apple's foundational design principles. However, lack of feedback from end-users does occasionally bite them (see: aborted Safari redesign)
- Apple takes QA very seriously and invests in high quality QA engineers. QA is not just "a step in the process" or a marginalized outsourced group.
- It's a culture of accountability, not committees. Every product and feature has a DRI (Directly Responsible Individual). When something isn't working out, the first question is "who's the DRI on this?"
- Most of the organization is highly siloed by function. This allows units to focus entirely on their objectives, which can be productive. But it makes cross-functional collaboration rare. In my opinion, this is why certain aspects of Apple's ecosystem feel disjointed, missing, or don't hang together holistically as well as they could.