#20 - Building Products People Love—Lessons from Decades at Apple and Adobe - Arno Gourdol

<p><em>“The most important thing we can do in order to get whatever success we want—build the best product you can. Invest all your energy in making the product absolutely best that you can think of. If you really focus on building an absolutely best product possible, everything else will follow."</em></p> <p>Arno is an inspiring tech leader with decades of experience in two major creative companies—Apple and Adobe. I’m honored to have him sharing his career journey and passion in this episode. Arno shared his amazing start of his career at Apple, especially when Steve Jobs came back and led the company back to focus, which was the key success factor that brought Apple to where it is today. The entire company had to adapt to Steve Jobs’s new ways of working and to work in an iterative fast paced approach, at the time when Agile was not yet widely known, including how Arno led a complete rewrite of the macOS Finder. Then Arno shared his next illustrious career at Adobe, where he had the opportunities to explore different projects and establish his engineering leadership skills. Arno led an audacious move when he proposed Adobe to open source XMP, a bold action when open sourcing wasn’t common back then. He also shared his lessons in dealing with halted projects, and the perspective that we should embrace when that happens. Arno then shared his invaluable wisdom on how to build products that people love and what to focus on in order to create successful products. Right at the end, Arno shared with me what made him decide to end his career and pursue the things he is truly passionate about.</p> <p>Listen out for:</p> <ul> <li>Arno’s career start - [00:08:07]</li> <li>Journey at Apple - [00:11:44]</li> <li>Steve Jobs impact - [00:14:17]</li> <li>Apple’s key success factor - [00:19:08]</li> <li>Working in agile manner - [00:20:40]</li> <li>Building without clear direction - [00:24:38]</li> <li>Tips when revamping product - [00:26:53]</li> <li>How to decide a technical rewrite - [00:30:36]</li> <li>Jour