<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Manhar Trivedi on Medium]]></title>
        <description><![CDATA[Stories by Manhar Trivedi on Medium]]></description>
        <link>https://medium.com/@manhartrivedi?source=rss-64cfb9ef4515------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ldLdgPOMj0b8nl_kli4f6A.jpeg</url>
            <title>Stories by Manhar Trivedi on Medium</title>
            <link>https://medium.com/@manhartrivedi?source=rss-64cfb9ef4515------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 09:39:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@manhartrivedi/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Creating Effective Technology Strategy]]></title>
            <link>https://medium.com/@manhartrivedi/creating-effective-technology-strategy-3a7dc46aa880?source=rss-64cfb9ef4515------2</link>
            <guid isPermaLink="false">https://medium.com/p/3a7dc46aa880</guid>
            <category><![CDATA[engineering-strategy]]></category>
            <category><![CDATA[strategycreation]]></category>
            <category><![CDATA[technology-strategy]]></category>
            <category><![CDATA[strategy]]></category>
            <dc:creator><![CDATA[Manhar Trivedi]]></dc:creator>
            <pubDate>Mon, 18 Dec 2023 11:38:07 GMT</pubDate>
            <atom:updated>2023-12-18T11:38:07.953Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1018/1*mpK1Va90T7EzRxq4BysZaQ.png" /><figcaption>Creating technology strategy</figcaption></figure><p>Technology strategy is one of those elusive, esoteric topics that we work in or are involved in daily, and yet it might seem difficult to formulate one. This is part-1 of 2 part series focused on a practioner’s guide to “H<em>ow to strategize”</em>. Part-2 would go deep dive into the “<em>What to strategize” </em>of technology strategy.</p><blockquote><strong>Problem:</strong> For our example i am choosing a fictional Digital product organisation that serves its customers in the SaaS business. As a CTO you <em>you’re entrusted with finding the next product line while migrating its </em>legacy operations and systems<br><strong>Your Job</strong>: Fix the technical organisation and propel the product into next phase of growth.</blockquote><p><strong>1) Defining the right problem</strong></p><p><strong><em>If I had an hour to solve a problem I’d spend 55 minutes thinking about the problem and five minutes thinking about solutions. </em></strong><em>Albert Einstein.</em></p><p>Don’t assume you have been given the right problem: This is often the most critical and overlooked step in creating a technology strategy. I often step into meetings focused on resolving complex tech systems and processes and I’d invariably encounter the initial argument to jump on microservices implementation or ask for a multi-million, multi-year system re-writes. When the actual problem might be deeply rooted in a product decision taken years ago that doesn’t apply in the current context.</p><blockquote><strong><em>Your actions: </em></strong><em>As a CTO you would need to take a wider view of the organization. Atleast initially it can be difficult to pin-point to the underlying issues at hand, which can range from talent, leadership, communication issues to architechure and product/market fit. You spend next 30 days on getting perspectives from all levels of organisation.</em></blockquote><p><strong>2) Embracing diverse perspectives</strong> (Go wide)</p><p>I often encourage to have orthogonal views on a topic coming from a diverse audience. Not only does it force you to think outside of the box, but it also raises the critical thinking of the whole group. <em>Go Wide: While seeking perspectives.</em></p><p>Did you end up with too many choices to choose from? Try affinity mapping or <a href="https://universalcoachingsystems.com/how-to-get-priorities-from-a-group-2/?ref=notesontech.io">money-spending exercise</a>s</p><blockquote><strong><em>Your actions: </em></strong><em>As a CTO you would need to take a wide view of the organization. Get diverse perspectives from Marketing, sales, customer service, customers. Its not uncommon to end-up with 100’s of feeback items from your network.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/834/1*CcSO79Cr2epj29XI6diVGg.jpeg" /><figcaption>Affinity mapping exercise</figcaption></figure><p><strong>3) Solutioning and Trade-off analysis </strong>(Go narrow: Less is more here)</p><p>This is often the stage of the activity where crowd-sourcing and a democratic approach don’t always succeed. Go narrow: Include your critical folks who can represent many. Speed is key here.</p><p>Trade-offs: Diverse groups can weigh in on different trade-offs. For example, Marketing departments might prioritize speed and experimentation while engineering might prioritize scalability and architecture. A shared dictionary of non-negotiables is often helpful here, which can range from data security to high-quality end-user experience as a common denominator for all groups.</p><p>Depending on the complexity and abundance of options, you may opt-in for conducting brief proof of concepts or assembling key practitioners to evaluate trade-offs among the myriad of choices available. If the group ended up choosing all problems to solve at once, you probably don’t need a strategy session but rather a planning to sequence your actions.</p><blockquote><strong>Your actions</strong>: There is new product launch for small market due in 3-months. While sales number and quality are projected to go down if not attended to immediately. Which one do you choose ? Are there clever alternates to both ? What are the trade-offs ?</blockquote><p><strong>4) Know thyself</strong></p><p><strong><em>Culture eats strategy for breakfast. </em></strong><em>Peter Drucker</em></p><p>Key questions to ask in this phase:</p><p>Do I understand my team’s capabilities? Do I understand my Organisational culture? Is there a mandate, willingness, and maturity to solve the issue?</p><blockquote><strong>Your actions</strong>: Now y<em>ou beleive that the group is very close to formulating the technical strategy which was created by support from cross-departments. Would marketing, sales department still support the strategy if plan goes south? Do you cross-departments have skin in the game and not just a superficial approvals ?</em></blockquote><p><strong>5) Anticipating and looking ahead</strong></p><p>Formulating a strategy can stem from an organization’s internal aspirations, external pressures, or responses to threats. Leaders must grasp both the internal dynamics and external challenges to effectively prioritize and present choices. Considering the strategy’s timeframe — whether short or long-term — requires anticipation not only of your own future steps but also those of your competitors and the evolving marketplace.</p><p><strong>6) Action plan</strong></p><p>This is part where the organization collectively agrees (<a href="https://aws.amazon.com/blogs/enterprise-strategy/guts-part-three-having-backbone-disagreeing-and-committing/?ref=notesontech.io">disagrees and commit</a>) to the initiatives and tasks it will own. This is where your operational tools like OKR’s, product plans and RACI can be used for a smooth execution.</p><blockquote><strong>Your actions</strong>: As a CTO you can further optimize the plan by squeezing the action plan timeline from 24 months to 9 months. This will invariably surface the most critical and actionable items the organisation can do.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rYS3r0QH7Px3owxj7oI_CA.jpeg" /><figcaption>Strategy prioritization</figcaption></figure><p><em>Note: Not only its important to outline what the organization is willing to undertake, but equally crucial to specify what it won’t pursue at present. If the group wants to execute all of the selected problems at once, chances are you might need to re-run the exercise#6.</em></p><p><strong><em>Execution is everything, planning is nothing. </em></strong><em>Anonymous</em></p><blockquote><em>More than </em>70% of organization<em> strategies fail.</em></blockquote><blockquote><em>What if 6 months into your execution plan your executive board draws out a plan to launch a new product offering. ? Do you abandon your plans or go back to board to ask for more funds or time ?</em></blockquote><p>Execution is as important as the strategy itself. The brilliance lies in understanding how to break down the execution cycles into a concise and efficient feedback loop. Flavors of Agile framework are perfect candidates for these.</p><p>Final thoughts:</p><ul><li>What not to do: Items and initiatives slated for later time should be the second most important deliverable from these exercises. If the group chooses to solve all problems at once or doesn’t identify a critical path, chances are you don’t need a strategy exercise rather simple planning should be suffice.</li><li>Trivial problems: Not all transformations require a formal strategy. Most of the trivial problems can directly go into the planning and execution phase.</li><li>Enterprise architecture is usually the backbone for any transformations. When executed in isolation seldom results in the intended outcome.</li><li>Tools before problem: OKRs, goals, product-plan are not strategies but simply tools to get your destination. Using them as a strategy would lead you off-path.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3a7dc46aa880" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Contrarian view to AI]]></title>
            <link>https://medium.com/@manhartrivedi/contrarian-view-to-ai-7a470930e00e?source=rss-64cfb9ef4515------2</link>
            <guid isPermaLink="false">https://medium.com/p/7a470930e00e</guid>
            <dc:creator><![CDATA[Manhar Trivedi]]></dc:creator>
            <pubDate>Mon, 30 Oct 2023 09:30:32 GMT</pubDate>
            <atom:updated>2023-10-30T09:30:32.195Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j3U6qjDP6C1LPrnmZ-RsBw.png" /></figure><p>An illuminating view from the greatest thinker, historian Yuval Harari and Mustafa Suleyman Entrepreneur and researcher of our times. Link to the full debate in the comment section</p><p>Types of task: AI is currently dominates the creation of new media (generative AI), reading content from images, transcribing audio/video. The panel talks about moving to more autonomous evolutions where new product development, organisations would be natively complete in AI.</p><p>Turning test: Originally devised in 1950 by Alan Turing it aimed to test the horizon limits of machine’s ability to exhibit intelligent behavior equivalent to that of a human. We are so close to the old Turing test that Mustafa has devised a new Turing test which would be good for next few decades. The new test aims at AI ability to do a disjointed set of individual tasks to accomplish something meaningful. You could ask AI to “Go make $1 million on a retail web platform in a few months with just a $100,000 investment.”</p><p>Value creation: The future of humanity will prioritize meaningful value creation over the necessity of jobs for mere survival. Imagine a scenario where AI is tasked with generating and innovating new product lines, allowing humans to concentrate on crafting services and experiences that we truly cherish.</p><p>Biggest threats: Technology is inherently neutral how we use technology is not. Humans are the only species that constantly put their survival at risk. We need to think ahead and put controls around the involvement of AI. Consider the complete elimination of AI’s capability to disseminate information on creating explosives and new viruses for household purposes.</p><p>Unequal Distribution: Yuval talks about how Hitler Rose to power in Germany because of three years of 25% unemployment. in our times, a rapid transition to AI workforce could have similar effects where entire jobs for a sector are positioned in single country effectively putting the entire population without a job in a specific sector. The domino effect on democracy and the geopolitical landscape is unfathomable.</p><p>Containment challenge: We already see our social media platforms littered with misinformation and fake news, making it challenging to discern facts. Consider the implications of AI models 10x more capable than the current version. It’s crucial for governments, the public, and organizations to get involved and shape the AI governance models, carefully shaping the limits, and type of information exposed to users.</p><p>Link to full debate: <a href="https://youtu.be/7JkPWHr7sTY?si=YFOLyraujGrn5oiT">https://youtu.be/7JkPWHr7sTY?si=YFOLyraujGrn5oiT</a></p><p>How do you think we can get involved and shape the future of AI ?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7a470930e00e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Unlocking levels in leadership]]></title>
            <link>https://medium.com/@manhartrivedi/unlocking-levels-in-leadership-f9e9f42229f?source=rss-64cfb9ef4515------2</link>
            <guid isPermaLink="false">https://medium.com/p/f9e9f42229f</guid>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[growth-mindset]]></category>
            <dc:creator><![CDATA[Manhar Trivedi]]></dc:creator>
            <pubDate>Fri, 20 Oct 2023 10:32:44 GMT</pubDate>
            <atom:updated>2023-10-20T10:32:44.149Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zNXxX1S2Da9pSNK6BbX1pw.png" /><figcaption>Levels in leadership</figcaption></figure><p>I am constantly surprised when people ask me what do really senior leaders do ? Are they working 80+ hours a week?</p><p>This is the conversation I found myself in over a coffee this week. Typically what would have been a one-liner response about working on top priority, vision, and communication, I ended up sharing a mental model.</p><p><strong>Junior Engineer/PM</strong>: You are told what to do, and given strict guardrails to work in. You excel in your assignment you get promoted.</p><p><strong>Senior Engineer/PM</strong>: Ownership: You have application or component-level ownership. Goals: You set goals for your application/product, and help set milestones for junior members. Responsibilities: You are responsible for enhancing, and maintaining products and applications. Within your team, you are giving enough guidance to junior members and maintaining standards.</p><p><strong>Manager/Principal Engineer/PM</strong> : Ownership: is now widened to cover multiple applications and components aligned to a customer value stream. You are responsible for providing value to end customers through developing, influencing, and upholding frameworks and standards. Team<strong>:</strong> Collaborating across multiple value streams and org functions. Goals and responsibility:<strong> </strong>Not only do you set goals for yourself and your teams but coordinate across the org to make sure the goals are aligned. Primarily responsible for the team output and not just your own.</p><p><strong>Senior Engineering leaders: </strong>Ownership<strong>: </strong>Own aggregate KPIs like customer and employee growth, productivity, retention, and satisfaction. Create frameworks and standards to operate multiple teams well. Create vision and long-term roadmaps. Team: Map organization OKR to teams. Empower your teams to collaborate and be enablers for other divisions (think sales, marketing, CS).</p><p><strong>Executives: </strong>Ownership: Primarily responsible for the overall vision, planning, and strategizing to stay competitive and lead market segment over decades to come. Tasked with secondary but vital functions of Legal, mergers, product development, staff development etc. Teams: Steer all the individual functions like product, technology, sales, marketing etc. Responsible for: Overall success of the organization both internal and external. Think external competition on one end and internal innovation on the other end of the spectrum.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f9e9f42229f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>