Big business style CTO or Silicon Valley style CTO?<p>Startup or enterprise? Technology play or product play? Consumer or commercial? Front end or platform or infrastructure?<p>Regardless, you need a framework for thinking about technology and the jobs to be done, no matter which dimension you’re interested in.<p>This is the ticket:<p><pre><code> Technology Strategy Patterns
by Eben Hewitt
October 2018
</code></pre>
<i>Technologists who want their ideas heard, understood, and funded are often told to speak the language of business—without really knowing what that is. This book’s toolkit provides architects, product managers, technology managers, and executives with a shared language—in the form of repeatable, practical patterns and templates—to produce great technology strategies.</i><p><i>Author Eben Hewitt developed 39 patterns over the course of a decade in his work as CTO, CIO, and chief architect for several global tech companies. With these proven tools, you can define, create, elaborate, refine, and communicate your architecture goals, plans, and approach in a way that executives can readily understand, approve, and execute.</i><p><a href="https://www.oreilly.com/library/view/technology-strategy-patterns/9781492040866/" rel="nofollow">https://www.oreilly.com/library/view/technology-strategy-pat...</a><p><a href="https://smile.amazon.com/Technology-Strategy-Patterns-Architecture-ebook/dp/B07JJNSP92/" rel="nofollow">https://smile.amazon.com/Technology-Strategy-Patterns-Archit...</a><p>With that in mind, you can then absorb any other book recommendations that may come from this thread, with a solid context and framing in which to map and understand them.