<?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 Nitin Malhotra on Medium]]></title>
        <description><![CDATA[Stories by Nitin Malhotra on Medium]]></description>
        <link>https://medium.com/@nitin09.malhotra?source=rss-63c3fc3aa094------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*0lCJx1YAl08ySDG9HOWfLg.jpeg</url>
            <title>Stories by Nitin Malhotra on Medium</title>
            <link>https://medium.com/@nitin09.malhotra?source=rss-63c3fc3aa094------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 20:08:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nitin09.malhotra/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[Don’t Tell Me AI Is Being Used. Show Me What It Changed.]]></title>
            <link>https://medium.com/@nitin09.malhotra/dont-tell-me-ai-is-being-used-show-me-what-it-changed-ab935fb7f440?source=rss-63c3fc3aa094------2</link>
            <guid isPermaLink="false">https://medium.com/p/ab935fb7f440</guid>
            <dc:creator><![CDATA[Nitin Malhotra]]></dc:creator>
            <pubDate>Sat, 20 Jun 2026 14:28:24 GMT</pubDate>
            <atom:updated>2026-06-20T14:28:24.089Z</atom:updated>
            <content:encoded><![CDATA[<p>Why engineering organisations must stop measuring AI activity and start measuring business impact</p><p>Every organisation is investing in AI.</p><p>We are hiring AI-native talent. We are upskilling existing teams. We are investing in AI tools. We are changing how engineering, product, testing, documentation, and release work.</p><p>But the success of an AI-native transformation should not be measured by how many tools we deploy or how many people use them.</p><p>The real measure is much more fundamental:</p><p><strong><em>How much additional capacity are we creating, and how effectively are we converting that capacity into business outcomes?</em></strong></p><p>AI should not be measured as an activity.</p><p>AI should be measured as an organisational multiplier.</p><p>Capacity Is the First Real Outcome</p><p>The first value AI adds to an engineering organisation is capacity.</p><p>Capacity means teams can deliver the same or better outcome with less effort, less friction, and less waiting time. It means you do More with Less.</p><p>That is why capacity is the foundation of how we measure AI-native transformation.</p><h4><strong><em>Capacity Gain % = ((Baseline Effort – AI-Native Effort) / Baseline Effort) × 100</em></strong></h4><p>For example, if a capability previously required 100 engineering days and, with AI-native ways of working, the same or better outcome now takes 70 engineering days, then we have created:</p><p>30% Capacity Gain. But capacity gain alone is not enough.</p><p>The real value comes when that capacity is deliberately reinvested into outcomes that matter.</p><p><strong><em>AI Success = Capacity Created × Business Outcomes Delivered</em></strong></p><p>This is the formula that keeps the transformation honest.</p><p><strong>What Creates This Capacity?</strong></p><p>It is created by the combination of people, technology, and operating model change.</p><p>We are investing across three dimensions.</p><ol><li><strong>Upskilling Existing Teams</strong></li></ol><p>AI-native transformation starts by helping current teams work differently.</p><p>Engineers, testers, architects, product owners, and leaders need to use AI to reduce friction across development, testing, review, documentation, release preparation, and knowledge discovery.</p><p>The goal is to increase the effectiveness of every person and every team.</p><p><strong>2. Hiring AI-Native Talent</strong></p><p>We are bringing in people who naturally think automation-first.</p><p>They look for ways to simplify workflows, reduce manual handoffs, improve engineering flow, and challenge traditional delivery models.</p><p>AI-native talent does not only add individual productivity.</p><p>It raises the operating level of the whole team.</p><p><strong>3. Changing the Engineering Operating Model</strong></p><p>The biggest impact comes when AI is embedded into how teams actually deliver software. AI should improve how we refine work, write code, generate tests, review changes, document decisions, prepare releases, detect defects, and operate platforms. It creates real capacity when combined with engineering discipline and operating model change.</p><p>Capacity Must Show Up in Delivery Outcomes</p><p>This is where many organisations get AI measurement wrong.</p><p>They measure what is easy to count:</p><ul><li>Prompt usage</li><li>* Tool adoption</li><li>* AI-generated code</li><li>* AI-assisted tickets</li><li>* Lines of code suggested by AI</li></ul><p>These metrics may show adoption, but they do not prove transformation. The real proof is whether AI-created capacity improves how the organisation delivers value.</p><p>That is why we focus on outcome-based metrics.</p><p>The Metrics That Matter</p><ul><li><strong>Time to Market</strong></li><li><strong>Time to Release</strong></li><li>Merge Request Lead Time</li><li>AI-Generated Code Successfully Merged Into Master. Generated code is not value. Accepted code is value.</li><li>Escape Defect Ratio. Speed without quality is not transformation.</li><li>OKR and Business Outcome Impact</li></ul><p>Every AI initiative should connect to an organisational priority.</p><p>Capacity should help accelerate customer experience, revenue growth, operational efficiency, platform reliability, innovation, or strategic roadmap delivery.</p><p>Together, Time to Market, Time to Release, Merge Request Lead Time, AI-assisted code merged, Escape Defect Ratio, and OKR Impact show whether AI-native transformation is producing real organisational value.</p><p><strong><em>What Many Organisations Get Wrong</em></strong></p><p>Many organisations start with tool usage and try to infer business impact later.</p><p>That approach creates dashboards, but not necessarily transformation.</p><p>High AI adoption does not automatically mean faster delivery.</p><p>More prompts do not automatically mean better decisions.</p><p>More generated code does not automatically mean more customer value.</p><p>More tickets closed does not automatically mean better outcomes.</p><p>The risk is simple:</p><p>Organisations start optimising for AI activity instead of AI impact. Adoption metrics may show whether people are using the tools.</p><p>Outcome metrics show whether the organisation is becoming better because of them.</p><p>⸻</p><p><strong>Final Thought</strong></p><p>AI-native transformation is not about using AI more. It is about making the organisation more capable. The investments we make in AI tools, AI-native talent, upskilling, and new ways of working must add up to something measurable.</p><p>They must add capacity.</p><p>And that capacity must show up in delivery speed, release flow, engineering quality, customer value, and OKR impact.</p><blockquote><strong><em>AI Success = Capacity Created × Business Outcomes Delivered</em></strong></blockquote><p>The organisations that win with AI will not be the ones with the most usage dashboards.</p><p>They will be the ones that can prove AI made them faster, better, and more capable of delivering meaningful outcomes.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ab935fb7f440" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Didn’t Stop Coding. AI Made That the Rational and Playful Choice.]]></title>
            <link>https://medium.com/@nitin09.malhotra/i-didnt-stop-coding-ai-made-that-the-rational-and-playful-choice-c9fb3248441f?source=rss-63c3fc3aa094------2</link>
            <guid isPermaLink="false">https://medium.com/p/c9fb3248441f</guid>
            <dc:creator><![CDATA[Nitin Malhotra]]></dc:creator>
            <pubDate>Tue, 23 Dec 2025 07:47:12 GMT</pubDate>
            <atom:updated>2025-12-23T07:47:12.981Z</atom:updated>
            <content:encoded><![CDATA[<p>There’s a quiet belief in engineering: as responsibility grows, distance from code is inevitable. Fewer commits. More reviews. Eventually, judgment without execution.</p><p>AI breaks that pattern — not by writing code for us, but by making it radically cheaper to turn judgment into systems. And something else happened along the way: <strong>It made engineering playful again.</strong></p><h3>Release Documents Are Not Process Artifacts</h3><p>They’re risk declarations. In my organization, we follow the <strong>4-eye principle</strong>. Traditionally, that meant me — or another lead — had to manually pore over every line of a release doc to ensure compliance.</p><p>When production fails, everyone suddenly re-reads the document. Too late.</p><p>So, I built a system where the <strong>Agent is the “second set of eyes.”</strong> Not because it was urgent — but because it was interesting.</p><h3>The Stack: Python, FastAPI, React — and LangGraph</h3><p>The UI is a React single-page application.<br> The backend is FastAPI, written in Python.</p><p>That part is intentionally boring.</p><p>What matters isn’t the framework choice — it’s what sits behind it: the <strong>agentic workflow</strong>, built using <strong>LangGraph</strong>.</p><p><strong>Why LangGraph?</strong> Because this problem isn’t a single prompt. It’s a graph of decisions. You need:</p><ul><li><strong>State:</strong> (Claims, evidence, confidence)</li><li><strong>Branching:</strong> (Missing evidence → retry → escalate)</li><li><strong>Parallel Reasoning:</strong> (Compliance ≠ Risk ≠ Consistency)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f8uPMg9ElX1sYZVEujR2wg.jpeg" /></figure><h3>This Is Not a Chatbot</h3><p>A chatbot answers questions. This system <strong>extracts claims, demands evidence, and evaluates risk.</strong> It’s not “AI approval”; it’s <strong>automated engineering review.</strong></p><h4>How the Agent Actually Thinks</h4><blockquote><strong><em>Parse and Normalize:</em></strong><em> Deterministic Python and schemas. No LLM magic yet.</em></blockquote><blockquote><strong><em>Extract Claims:</em></strong><em> “Tests passed,” “Rollback exists,” “No breaking changes.”</em></blockquote><blockquote><strong><em>Fetch Evidence:</em></strong><em> The agent looks for attachments, links, and logs.</em></blockquote><blockquote><strong><em>Run Specialist Agents in Parallel:</em></strong><em> * </em><strong><em>Compliance Agent:</em></strong><em> Checks the “boring” checklists.</em></blockquote><blockquote><strong><em>Risk Agent:</em></strong><em> Imagines realistic failure modes.</em></blockquote><blockquote><strong><em>Aggregate and Score:</em></strong><em> Low confidence escalates to a human review.</em></blockquote><h3>Playfulness Is Back — If We Let It Be</h3><p>AI quietly lowered the cost of curiosity. You can try a weird idea, encode a half-formed intuition, and throw it away if it doesn’t work. That’s not recklessness; that’s healthy engineering.</p><p>Agentic systems don’t reward prompt tricks. They reward <strong>system thinking, domain understanding, and judgment.</strong> Those are senior skills. AI doesn’t replace them — it finally makes them cheap to express.</p><p><strong>The only real question now is: are we still curious enough to play?</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c9fb3248441f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Stop Being a Leader. Start Being an Anti-Leader!]]></title>
            <link>https://medium.com/@nitin09.malhotra/stop-being-a-leader-start-being-an-anti-leader-a229bfcce32e?source=rss-63c3fc3aa094------2</link>
            <guid isPermaLink="false">https://medium.com/p/a229bfcce32e</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[anti-leadership]]></category>
            <category><![CDATA[mindset]]></category>
            <category><![CDATA[leadership-styles]]></category>
            <dc:creator><![CDATA[Nitin Malhotra]]></dc:creator>
            <pubDate>Sun, 13 Jul 2025 06:53:39 GMT</pubDate>
            <atom:updated>2025-07-13T06:53:39.706Z</atom:updated>
            <content:encoded><![CDATA[<p>A quirky guide to embracing T-shaped leadership and becoming the innovation magnet your team needs.</p><p>Think you’ve mastered leadership? Well, guess what — leadership just got flipped upside down. Welcome to <strong>Anti-Leader Leadership</strong> — the quirky sibling of traditional leadership, the one who arrives late to meetings but somehow always has the best ideas. Let’s break it down.</p><h3>Wait, Anti-Leader? What’s That?</h3><p>Imagine leaders who don’t want statues built in their honour but prefer scribbling ideas on napkins at coffee shops. They’re T-shaped — meaning they have deep expertise (the vertical line of the T) but are also curious wanderers across many topics (the horizontal bar). They don’t command; they serve. They don’t instruct; they inspire.</p><p>Anti-Leaders are those strange yet fascinating creatures who say, <em>“I don’t have followers; I have fellow explorers.”</em></p><h3>Am I an Anti-Leader? Take this quirky quiz:</h3><ul><li><strong><em>Do you prefer questions over orders?</em></strong></li><li><strong><em>Have you ever started a team meeting with, “Let’s break the rules today!”?</em></strong></li><li><strong><em>Does your comfort zone have a “Caution: Entering Innovation Zone” sign?</em></strong></li><li><strong><em>Would your team describe you as “weirdly inspiring”?</em></strong></li></ul><h3>Why Anti-Leaders Are Innovation Magnets: The Courage Factor</h3><p>An Anti-Leader’s courage isn’t just bravado. It’s the quiet confidence to say, <em>“I have no clue — but let’s figure it out together.”</em></p><p><strong>Example</strong></p><ul><li><strong>As an engineering lead</strong>, you scrapped a perfectly working system. His reason? <em>“Because perfectly working doesn’t mean perfect.”</em> His team built something even better in record time because courage is contagious.</li><li><strong>You as Product</strong> prefers brainstorming sessions over cappuccinos at quirky cafés instead of formal boardrooms — and that’s exactly how your favourite app update was born.</li><li>Imagine waking up in the middle of the night with a crazy idea to transform the customer experience, and then confidently demoing it the next morning — that’s the Anti-Leader spirit in action.</li></ul><p>See the trend? Anti-Leaders have the guts to dive into uncertainty because innovation hides just beyond your comfort zone.</p><h3>Intrinsic Motivation: The Fire Within</h3><p>Anti-Leaders don’t do this for plaques or applause — they’re driven by internal fire. It’s the rush they get when they solve an impossible problem or help someone else shine brighter.</p><p>Remember when Elon Musk sent a car to space, not because he had to, but because, “Why not?” That’s intrinsic motivation — quirky, bold, utterly Anti-Leader.</p><h3>How to Unleash Your Inner Anti-Leader (Because we know you’re curious):</h3><ul><li><strong>Break small rules:</strong> Encourage “disruption Thursdays.” Try something quirky once a week.</li><li><strong>Celebrate weirdness:</strong> Have a “Best Failure Award.” Reward bravery over success.</li><li><strong>Stay hungry &amp; foolish:</strong> Adopt Steve Jobs’s advice. Keep exploring, stay curious.</li></ul><h3>The Anti-Leader Manifesto (Stick it to your office wall!):</h3><blockquote><strong><em>We are explorers, not commanders.</em></strong><em><br></em><strong><em>We inspire curiosity, not obedience.</em></strong><em><br></em><strong><em>We thrive on courage, quirky innovation, and pizza analogies.</em></strong><em><br></em><strong><em>Our legacy is how we make others feel, not how many follow us.</em></strong></blockquote><p>Embracing Anti-Leader Leadership isn’t just about changing your style — it’s about changing your mindset. So, go ahead: be daring, stay curious, and lead with passion. Because when you stop chasing titles and start chasing ideas, magic happens.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a229bfcce32e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Unseen Hand: Leading Tech Projects When You Don’t Call All the Shots]]></title>
            <link>https://medium.com/@nitin09.malhotra/the-unseen-hand-leading-tech-projects-when-you-dont-call-all-the-shots-8e6442083063?source=rss-63c3fc3aa094------2</link>
            <guid isPermaLink="false">https://medium.com/p/8e6442083063</guid>
            <dc:creator><![CDATA[Nitin Malhotra]]></dc:creator>
            <pubDate>Fri, 23 May 2025 12:40:03 GMT</pubDate>
            <atom:updated>2025-05-23T12:42:13.540Z</atom:updated>
            <content:encoded><![CDATA[<p>You know the feeling. A critical project deadline looms, your personal and team goals are crystal clear, yet you’re staring at a wall of external dependencies. Architecture discussions drag on endlessly, requirements shift daily, and the teams you rely on — often reporting to entirely different leadership — seem to operate in a different time zone, or even on a different planet.</p><p>The frustration is real. You’re accountable for outcomes, yet you don’t hold all the levers of control. How do you instil urgency and alignment in an organisational symphony where you’re not conducting every section? This isn’t a flaw in your leadership — it’s a fundamental challenge in modern, interconnected tech organisations. Your power lies not in command but in strategic influence, radical transparency, and disciplined execution.</p><h3>The Program Manager as Chief Orchestrator</h3><p>In this complex landscape, Program Management is the indispensable backbone that keeps the symphony on tempo. A skilled program manager acts as the <em>architect of alignment</em>, the <em>master of visibility</em>, and the <em>bridge across silos</em>. They don’t just manage tasks — they create a shared reality that unites disparate teams.</p><p>A robust program management function delivers:</p><ul><li><strong>End-to-end transparency</strong>: Tools like dependency maps and real-time dashboards expose blockers proactively. For example, a 2024 study by the Project Management Institute (PMI) found that organisations with <strong><em>mature program management practices are 2.5x more likely to deliver projects on time by identifying dependencies early.</em></strong></li><li><strong>Consistent prioritisation</strong>: Clear frameworks ensure everyone understands what drives the overarching goal. This aligns with findings from McKinsey, which highlight that teams with shared priorities are 1.7x more likely to meet strategic objectives.</li><li><strong>Proactive risk mitigation</strong>: By spotting potential pitfalls early, program managers rally resources to address them before they derail progress. <strong><em>A 2023 PMI report noted that proactive risk management reduces project failure rates by up to 30%.</em></strong></li></ul><p>Strong program management fosters a culture of collective accountability. It empowers teams by clarifying how their contributions fit into the larger puzzle, driving urgency and purpose. For instance, a program manager might use a tool like Jira or Confluence to create a shared dependency tracker, ensuring no team operates in isolation.</p><h3>Product Management: The Discipline of “Done”</h3><p>“Architecture debates drag on.” “Requirements keep expanding.” These are symptoms of an undefined finish line. Strong Product Management is your frontline defence against scope creep and indecision.</p><p>Product Management’s focus on a <strong>Minimum Lovable Product (MLP)</strong> — an evolution of the Minimum Viable Product (MVP) — is about disciplined scope control. An MLP defines the smallest set of features that delights customers while achieving core business objectives. According to a 2024 <strong><em>Harvard Business Review article, companies that prioritise MLPs over bloated feature sets see 20% faster time-to-market and higher customer satisfaction.</em></strong></p><p><strong>The Engineering Reality</strong>: Imagine a product team endlessly tweaking “nice-to-have” features, delaying a critical API your mobile app needs to launch.</p><p><strong>Your Move</strong>: Collaborate with Product Management to champion the MLP. Establish a firm scope baseline and enforce rigorous change control. For every new requirement, ask: <em>“What committed feature are we deprioritising to accommodate this?”</em> This forces trade-offs and reveals the true cost of additions. Program Management provides the structure for these discussions, while Product Management defines the “what” and “why.” For example, Spotify’s product teams use a “DIBB” framework (Data, Insights, Beliefs, Bets) to ruthlessly prioritise features, ensuring alignment with business goals.</p><h3>Taming the Architecture Beast</h3><p>Endless architectural debates often stem from unclear product goals or missing decision-making authority. <strong><em>A 2025 Gartner report notes that 60% of project delays in tech organisations are due to prolonged architectural indecision.</em></strong></p><p><strong>Your Move</strong>: Push for a “good enough for now” decision with a clear cutoff date. Quantify the cost of indecision: <em>“Every week we delay architecture lock-down adds X weeks to development and Y weeks to integration testing.”</em> Use data to drive urgency — <strong><em>research from Standish Group’s 2024 Chaos Report shows that projects with clear decision deadlines are 40% more likely to stay on schedule</em></strong>. Strong program management facilitates this by convening stakeholders, documenting decisions, and ensuring accountability. For instance, a program manager might use a Decision Log to track architectural choices and their rationales, preventing revisits.</p><h3>Orchestrating Urgency Across Silos</h3><p>This is where your influence shines. You can’t simply demand speed — you must create conditions where it becomes a shared priority.</p><p><strong>The Engineering Reality</strong>: Your mobile app team is blocked by a critical backend API from a platform team, threatening your Q3 revenue goal.</p><p><strong>Your Move</strong>:</p><ul><li><strong>Elevate the “Why”</strong>: Don’t just send a Slack message. Arrange a concise, high-impact call with the platform team lead and their manager. Frame their deliverable as critical to a shared goal: <em>“Our Q3 revenue target hinges on this API. How can we remove your team’s obstacles?”</em> <strong><em>A 2024 study by Deloitte found that cross-team alignment on shared goals increases delivery speed by 25%.</em></strong></li><li><strong>Radical Transparency</strong>: Use shared tools like Trello, Asana, or custom dashboards to visualise cross-team dependencies and blockers. This isn’t about finger-pointing — it’s about making problems visible so leadership can reprioritise. For example, Amazon’s “Working Backwards” process uses shared PR/FAQ documents to align teams on dependencies early.</li><li><strong>Offer Help</strong>: Can your team provide test data, specs, or temporary resources? Slowdowns often stem from overload or unclear requirements. <strong><em>A 2023 X post by a tech leader emphasised that offering support to blocked teams can reduce delivery friction by 15–20%.</em></strong></li></ul><h3>Beyond Blame: Accountability &amp; Learning</h3><p>When goals slip, the urge to point fingers is strong. But true accountability is about ownership and learning, not punishment. If delays occur, responsibility lies across the chain, from teams to leadership, who didn’t align priorities or resources.</p><p>Conduct a <strong>blameless post-mortem</strong>. Ask: <em>“What happened? Why? What can we do differently?”</em> A 2025 PMI study found that organisations using blameless retrospectives improve project success rates by 35% over time. Tools like Miro or Retrium can facilitate these sessions, capturing insights to prevent repeat issues.</p><h3>Conclusion</h3><p>Leading projects in complex, matrixed tech environments is an art form. By leveraging strong program management, championing product discipline, fostering transparency, guarding scope, and building alliances, you can deliver results even when you don’t control every lever. Go forth and conduct your unruly symphony — the impact will be profound.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8e6442083063" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AI is writing code now?! — My brain feels like it’s doing backflips.]]></title>
            <link>https://medium.com/@nitin09.malhotra/ai-is-writing-code-now-my-brain-feels-like-its-doing-backflips-ae41ff62cb30?source=rss-63c3fc3aa094------2</link>
            <guid isPermaLink="false">https://medium.com/p/ae41ff62cb30</guid>
            <dc:creator><![CDATA[Nitin Malhotra]]></dc:creator>
            <pubDate>Sun, 18 May 2025 16:03:29 GMT</pubDate>
            <atom:updated>2025-05-18T16:03:29.029Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>AI is writing code now?! — My brain feels like it’s doing backflips.</strong></h3><p>Okay, fellow young devs, let’s have a real talk. Remember those late nights wrestling with syntax errors, feeling like you’re deciphering ancient scriptures just to get a simple “Hello, world!” to appear? Yeah, me too. But lately, something wild has been happening. AI is in the coding room, and honestly, it feels like the ground beneath our keyboards is shifting.</p><p>I’ve been playing around with these AI-powered code generators, and it’s mind-blowing. Watching it spit out functional code in seconds feels like witnessing magic. Suddenly, tasks that used to take hours are… well, done. It’s like having a super-efficient, tireless pair programmer who has seen every Stack Overflow answer ever written.</p><p>But here’s the kicker, the thing that keeps me up at night (more than those pesky semicolons ever did): does this mean our coding journey is becoming obsolete? Are we going to be replaced by these digital wizards?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7wMs4wcu7NzNqYC5anVSPA.gif" /><figcaption>AI prompt code-generation using Cursor App</figcaption></figure><p>My gut feeling, and what I’m starting to see in the real world, is a bit more nuanced. Think of it this way: the AI can build the Lego blocks incredibly fast. It can assemble walls and maybe even the basic structure of a house. But we are the architects. We understand the customer&#39;s needs, the structural integrity, the aesthetics, and most importantly, we can spot if the AI-built wall is about to collapse!</p><p>Debugging AI-generated code feels like a whole new level of detective work. It’s not just about tracing your logic; it’s about understanding why the AI made a particular choice, identifying subtle errors you might not have even considered, and ensuring it truly aligns with the project’s goals and extending this code, adding those unique features and that human touch? That’s where our creativity and problem-solving skills truly shine.</p><p>I’m starting to believe that the old 90/10 rule – 90% coding, 10% debugging – might just flip on its head. We might spend 90% of our time meticulously analysing and refining the 10% of code that requires that irreplaceable human spark – the innovative solutions, the elegant optimisations, the understanding of the bigger picture.</p><p>This brings up a crucial point for us developers. We can’t just rely on AI to do the heavy lifting. Building a solid foundation in programming fundamentals is more critical than ever. We need to understand the “why” behind the code, not just the “how”. Otherwise, we risk becoming mere code reviewers, unable to truly grasp the intricacies or identify potential issues lurking beneath the surface.</p><p>So, what’s the game plan? Embrace the change! Experiment with these AI tools. Learn how to prompt them effectively, how to read their output critically, and how to integrate them into our workflow. This isn’t about fearing the robot uprising; it’s about learning to dance with the robots, becoming better, more efficient, and ultimately, more valuable developers.</p><p>And that burning question I keep pondering? Will AI steal our jobs, or will it give us even more fascinating challenges to tackle? Honestly, I don’t have a definitive answer. But I’m leaning towards the latter. The problems we can solve with this amplified power are immense. It’s an exciting, albeit slightly nerve-wracking, time to be a developer. Let’s buckle up and figure this out together!</p><p><strong>AI is changing the game, no doubt. But remember, games are always more fun with a skilled player. Let’s play :)</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ae41ff62cb30" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Unleashing the Power of Digital: A Cultural Journey for Deutsche Telekom Digital Labs]]></title>
            <link>https://blog.dtdl.in/unleashing-the-power-of-digital-a-cultural-journey-for-deutsche-telekom-digital-labs-7f4d20483d83?source=rss-63c3fc3aa094------2</link>
            <guid isPermaLink="false">https://medium.com/p/7f4d20483d83</guid>
            <category><![CDATA[culture]]></category>
            <dc:creator><![CDATA[Nitin Malhotra]]></dc:creator>
            <pubDate>Sat, 06 Jan 2024 01:53:16 GMT</pubDate>
            <atom:updated>2024-01-06T02:23:47.326Z</atom:updated>
            <content:encoded><![CDATA[<p>Five years ago, at DTDL, a diverse group of us embarked on a shared mission: to create a dynamic and innovative culture.</p><p>Through brainstorming and teamwork, a team of passionate engineers crafted principles to cultivate a culture built on digital simplification &amp; customer obsession, embraced a founder’s mindset, and practised honest accountability, all to build a culture that thrives on trust, innovation, and customer delight.</p><p><strong>Guiding Our Journey: Our Purpose:</strong></p><blockquote>At the core of the cultural transformation lies with unwavering purpose of a company and our purpose statement is : <strong>Unleash the power of digital to simplify customers’ lives, create better customer experiences, and gain trust<em>.</em></strong> This purpose serves as a guiding light, shaping every decision and action within DTDL.</blockquote><p><strong>Our Guardrails: The Values We Hold</strong></p><p>Our values aren’t just words on a wall but the rocket fuel igniting our shared vision. Digital simplification, customer obsession, and a founder’s spirit are the beacons that guide us, the embers that spark innovation in every individual’s contribution.</p><ul><li><strong>Digital Simplification:</strong> Embracing the transformative power of digital technology to enhance the lives of our customers.</li><li><strong>Customer Obsession:</strong> Demonstrating empathy, respect, openness, and diversity while prioritizing speed and reliability.</li><li><strong>Founder’s Mindset:</strong> Fostering a culture of risk-taking, innovation, problem-solving, curiosity, bravery, and an agile mindset.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xqxqC9sMrVSC7etVMEAdTA.png" /></figure><p><strong>Our Culture: The Rocketship to Success</strong></p><p>The company’s culture is likened to a rocket ship. This culture is portrayed by a spirit of entrepreneurship, problem-solving, and the ability to think outside the box. We’re entrepreneurs at heart, tackling problems with bold ideas and always looking beyond the horizon. Here’s how we fuel this rocket ship:</p><p><strong>Our Culture is by our People</strong>: <strong>Hiring the Best Talent Internationally:</strong></p><p>Recognizing the unique strengths and perspectives of a diverse group of individuals focused on strategies to get the best of teams. The key takeaways include:</p><p><strong>Attracting Top Talent:</strong></p><ul><li><strong>Highlight Technical Stack Innovation</strong>: Showcasing our cutting-edge open-source technologies and frameworks. Engineering blog posts, open-source contributions, and participation in relevant conferences to attract the right talent.</li><li><strong>Host Hackathons and Coding Challenges:</strong> We attract talent by organizing Tech MeetUps, hackathons and online coding challenges focused on your tech stack.</li><li><strong>Partner with Talent Platforms</strong>: Utilize specialized platforms connecting engineering talent with relevant opportunities. Engage with tech communities and universities.</li></ul><p><strong>Engaging New Hires</strong>:</p><ul><li><strong>Pre-Boarding Tech Bootcamps</strong>: Welcoming new hires with immersive bootcamps introducing our tech stack, development practices, and team culture.</li><li><strong>Shadowing Days and Mentorship Programs</strong>: Pair new hires with experienced engineers for mentorship, firsthand project tasks, and exposure. Allocate Buddies, who can guide and help throughout the onboarding process.</li><li><strong>TechX Talks and DTUniversity: </strong>Fostering continuous learning with internal tech talks and informal discussions where engineers share their expertise and projects.</li></ul><p><strong>Enhancing International Collaboration:</strong></p><ul><li><strong>Teambuilding Activities:</strong> Facilitate cross-cultural connections through Informal catchups or cultural exchange sessions.</li><li><strong>Global Hackathons and Innovation Contests</strong>: Participating in global hackathons and Tech events to encourage collaboration across international teams focused on solving global challenges.</li></ul><p><strong>Embedding our company’s values and culture into every aspect of our activities is important. To ensure this, we’ve crafted a series of impactful rituals:</strong></p><p><strong>X Days:</strong> These are direct and indirect touchpoints that ensure continuous engagement between our customers and employees. They are pivotal moments that shape perspectives and interactions.</p><p><strong>Demos Days and Internal Tech Fairs: </strong>These are dedicated days for teams to showcase their projects and innovations internally, fostering cross-pollination of ideas and technical skill sharing.</p><p><strong>Bug Bash Extravaganza</strong>: Enabling a customer-obsessed culture by combining product demos with a <strong>“Bug Bash”</strong> day, encouraging our customers to identify and playfully collaborate with engineers on fixing bugs in a real-time, gamified environment.</p><p><strong>Campaign Day Blitz:</strong> Engineers are on fire during a campaign day, eyes glued to a monster screen. Weeks of prep unleashed. The graph spikes, shattering the target. More than metrics, it’s the sweat, the passion. The room ignites! Victory tastes sweet, literally — cake awaits.</p><p><strong>Tech Talent Exchange Programs</strong>: We have encouraged our engineers to spend time working with teams in different countries, gaining new perspectives and expanding their skill sets.</p><p><strong>Measuring Pulse:</strong> Measuring the pulse of our team goes beyond traditional surveys. AI capabilities analyze E-NPS data and conduct virtual focus groups, allowing us to gather more minute feedback and quickly identify areas needing attention.</p><p><strong>Monthly Product Townhalls:</strong> These gatherings serve as a platform for communication and alignment across teams, fostering unity and understanding.</p><p><strong>Recognition TAvengers Program:</strong> Celebrating successes and achievements reinforces our culture of appreciation and motivates continued excellence.</p><p><strong>Aligned OKRs:</strong> By implementing a standardized OKR framework across teams, we foster collaboration and ensure everyone works towards common goals.</p><p><strong>Informal Catch-Ups:</strong> Creating spaces for informal interactions without leaders encourages casual connections and relationship-building among colleagues.</p><p>We’ve cracked the code on an electrifying engineering culture. No more silos, no more guesswork. Seamless collaboration, shared passion, and a relentless drive.</p><p>Every challenge is an opportunity to impress. Our engineers stand shoulder-to-shoulder, a force of nature ready to craft customer experiences that rewrite the rulebook.</p><p>Prepare to witness epic. Prepare to witness the groundbreaking. Prepare to witness DTDL engineering. This is where business success takes flight, powered by a culture that redefines what’s possible!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7f4d20483d83" width="1" height="1" alt=""><hr><p><a href="https://blog.dtdl.in/unleashing-the-power-of-digital-a-cultural-journey-for-deutsche-telekom-digital-labs-7f4d20483d83">Unleashing the Power of Digital: A Cultural Journey for Deutsche Telekom Digital Labs</a> was originally published in <a href="https://blog.dtdl.in/">Deutsche Telekom Digital Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mental model to create a safe space for your team]]></title>
            <link>https://medium.com/@nitin09.malhotra/mental-model-to-create-a-safe-space-for-your-team-3461ddfba349?source=rss-63c3fc3aa094------2</link>
            <guid isPermaLink="false">https://medium.com/p/3461ddfba349</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[team-management]]></category>
            <category><![CDATA[safe-space]]></category>
            <category><![CDATA[better-workplaces]]></category>
            <category><![CDATA[mental-model-diagrams]]></category>
            <dc:creator><![CDATA[Nitin Malhotra]]></dc:creator>
            <pubDate>Thu, 24 Mar 2022 06:20:16 GMT</pubDate>
            <atom:updated>2022-03-24T06:21:40.608Z</atom:updated>
            <content:encoded><![CDATA[<h3>Hey, young and emerging leaders! This one is for you,</h3><p>While working as Director of Engineering in Deutsche Telekom Digital Labs, one of my responsibilities is creating a safe space for the team.</p><p>It is a space where people feel encouraged, an environment that protects people and engages them with the same mindset people.</p><blockquote>Today, I will use this article to share my experience and talk more about “<strong>How to create a safe space for your teams.</strong>” I have personally applied these learnings as practice and hope that will help you.</blockquote><p>Whenever I reflect on my career, I feel safer when teams are supportive and collaborative. I learned from that experience instead of being blamed or reprimanded when I made a mistake. I realized that I have learned quickly and thrived in such an environment.</p><p>A safe space means where people feel valued, trusted, and empowered. The team with strong psychological safety is less worried about the negative consequences of taking risks, making mistakes, sharing their genuine opinions team, and being candid with each other.</p><p>I feel the following pillars would help you create a safe space, and you can accumulate many things around these pillars.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QVKozSjS28pFxul7uy73ZQ.jpeg" /></figure><ul><li><strong>Growth Opportunities and Objectives:</strong> — “Why?” factor engages your team more. Believe in their abilities and set objectives. Show the big picture. In a way, you provide an opportunity to align organizational goals and your team that you believe. You get a space to try and learn something unique. If it is a failure, it is not a failure, and your team got the chance to try, learn and fail.</li><li><strong>Guardrail your team:</strong> — It is essential to know the strength and weaknesses of your team. Always try to strengthen the weaker section. Coach and mentor effectively. Give them a chance to prove themselves. Regular feedback and 1–0–1 sessions would help you build a strong relationship with your team. Always praise and reward for the splendid work they have done.</li><li><strong>Manage the external pressure:</strong> Be honest and transparent with your stakeholders and team. Lead by example to handle the pressure. Communicating timely, clear, and with the right priorities would help you align your team with ease.</li><li><strong>Manage risks:</strong> Sometimes, the risk is inevitable, and you cannot avoid it. Always keep an attitude to mitigate and manage the risk. Openly communicate and ask for help from your team members. Do not blame; it makes the team disengage and disempowered.</li></ul><p>Do share how your journey has been. Let us use this forum to discover more from each other’s experiences &amp; make our workplace a #bestworkplacetowork, so stay connected and happy learning 😊.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3461ddfba349" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ONESHOP: One of Its Kind]]></title>
            <link>https://blog.dtdl.in/oneshop-one-of-its-kind-f2076594079b?source=rss-63c3fc3aa094------2</link>
            <guid isPermaLink="false">https://medium.com/p/f2076594079b</guid>
            <dc:creator><![CDATA[Nitin Malhotra]]></dc:creator>
            <pubDate>Wed, 23 Sep 2020 10:04:52 GMT</pubDate>
            <atom:updated>2020-09-23T10:04:52.838Z</atom:updated>
            <content:encoded><![CDATA[<p>Who would have imagined that the Covid-19 pandemic situation would make such a fundamental shift in way of working?</p><p>By now, most of the organizations would have hit hard due to this outbreak. It’s been a significant challenge to keep up the productivity of the team and embracing the remote way of working.</p><p><strong><em>I am inspired that the OneShop (e-commerce platform) team has made it possible to launch it in T-Mobile Poland, T-Mobile Slovakia, and T-Mobile Croatia during this extraordinary situation along with the T-Mobile Czech Republic. (already live since last 9 months)</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oRhbj52l73cHUIuyoL3Umg.png" /></figure><p>This would have not been possible without the constant support of all the team members working vigorously to achieve this milestone. Kudos to all the members to make this happen.</p><p>T-mobile Romania and T-mobile Macedonia are the succeeding countries that have been on-boarded and under preparation to take the OneShop platform live soon.</p><h4><strong><em>Let me give you a background on the incubation of the OneShop Platform</em></strong></h4><p>When I joined Deutsche Telekom Digital Labs in June 2018, as part of my very first assignment, I got an opportunity to travel across our national companies (NatCos) for product workshops. As an outcome of the workshop and owing to the rise of the e-commerce industry in the European market, the team behind OneShop identified the underlying business problem to unify all the NatCos &amp; build a digital sales platform.</p><p><strong>Three main focus areas on this initiative:</strong></p><blockquote><strong>· Best in class digital commerce solution</strong></blockquote><blockquote><strong>· Harmonised online shopping platform</strong></blockquote><blockquote><strong>· Significant conversion uplift</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MpDG5HrgtJQcmxdK3N8n5A.png" /><figcaption>OneShop home page for Czech, Poland(Heyah), Poland(T-mobile), Slovak, and Croatia</figcaption></figure><h4><strong>Voila! Here’s How This Happened:</strong></h4><p>It is the first project initiative at DT which began the transformation of legacy platforms to state-of-the-art digital architecture, customizable according to the specific needs of various countries.</p><h4>Right architecture is key to success</h4><p><strong>· </strong>OneShop e-commerce ecosystem has been built from scratch. Its single code base has been serving customers across countries. OneShop architecture is omnichannel, multitenant, multilingual, and supports multi-currency.</p><p><strong>.</strong> Varied European countries, ranging demographics, and henceforth an in-depth customer requirement analysis, led us to develop a feature flag development enabled application, vouchsafes our common codebase.</p><figure><img alt="OneShop microservices architecture supports multi-tenancy" src="https://cdn-images-1.medium.com/max/1024/1*YfChD2X47Ew-3Bt32_fEsA.png" /><figcaption>OneShop high-level architecture</figcaption></figure><h4>Mobile First Frontend</h4><p><strong>· </strong>To garner the user interest with our magenta theme colors, Augmenting the appeal towards the app and web, the UX/UI was revamped.</p><p><strong>·</strong> OneShop being progressive web app (Google case study for PWA <a href="https://developers.google.com/web/showcase)">https://developers.google.com/web/showcase)</a> is developed in React, currently supporting 5 breakpoints (320px, 768px, 1024px, 1366px, 1680px) keeping in mind the possible smartphones in the market. Its core has been nourished giving thought to the brand Deutsche Telekom has established over the years and how our European customers would want to believe in the brand.</p><p><strong>· </strong>Our very own shop, OneShop has developed a component library from scratch. This component library is reusable across. Find out the cool stuff we did here <a href="https://medium.com/deutsche-telekom-gurgaon/building-a-re-usable-component-library-from-scratch-in-react-for-deutsche-telekom-dc1cf5640140">https://medium.com/deutsche-telekom-gurgaon/building-a-re-usable-component-library-from-scratch-in-react-for-deutsche-telekom-dc1cf5640140</a></p><h4>Open Source by default</h4><p><strong>·</strong> OneShop solved the majority of the scaling and architecture problem using open source technologies (Spring Cloud capabilities, NoSql databases, Kafka, Elastic Search, ELK stack, Grafana, Prometheus, rabittMq) and with micro-services architecture. More than 6 digital platforms (Shopping Cart, Sales catalog, order tracker, search platform, page builder, content management system, inventory management, and distributor) are implemented along with 18 microservices around it.</p><p><strong>· </strong>Its search platform is built over the industry-proven ElasticSearch engine handling enormous customer requests per day. Its average response time is &lt;50ms.</p><h4>Distributed Ecosystem</h4><p><strong>· </strong>Talk about a distributed server ecosystem, we are intelligently leveraging spring cloud and NetFlix capabilities, to orchestrate our microservices.</p><p><strong>· </strong>We are deployed over AWS and fully cloud-native, we can easily right size our microservices, leverage autoscaling instances, lambda functions, and use powerful cost management tools to monitor our costs, so we can always be on top of your how much we’re spending.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BSOJcoMnU9thB0-qRvM4JQ.png" /><figcaption>OneShop 360 degrees coverage view</figcaption></figure><h4>Analytics, tracking, and Monitoring from inception</h4><p><strong>· </strong>Humongous data keeps coming our way and to provide a hassle-free resolution, thereby aiming for impeccable customer experience, we maintained real-time analytics, tracking, monitoring, infra automation, CI&amp;CD from the very inception. We are re-using OneView (Built-in OneApp) for customer analysis.</p><blockquote>In a nutshell, we are believing in the power of ‘ONE’ and demonstrating how it will create a significant impact on us in our digital transformation journey. :)</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f2076594079b" width="1" height="1" alt=""><hr><p><a href="https://blog.dtdl.in/oneshop-one-of-its-kind-f2076594079b">ONESHOP: One of Its Kind</a> was originally published in <a href="https://blog.dtdl.in/">Deutsche Telekom Digital Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Deutsche Telekom Digital Labs: Building a Customer Obsessed Developer Cult]]></title>
            <link>https://blog.dtdl.in/deutsche-telekom-digital-labs-building-a-customer-obsessed-developer-cult-22ccd467801e?source=rss-63c3fc3aa094------2</link>
            <guid isPermaLink="false">https://medium.com/p/22ccd467801e</guid>
            <category><![CDATA[compassionate-leadership]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[emphaty]]></category>
            <category><![CDATA[growth-mindset]]></category>
            <category><![CDATA[customer-obsession]]></category>
            <dc:creator><![CDATA[Nitin Malhotra]]></dc:creator>
            <pubDate>Tue, 01 Sep 2020 13:39:35 GMT</pubDate>
            <atom:updated>2021-04-29T09:42:13.150Z</atom:updated>
            <content:encoded><![CDATA[<h4>What makes DTDL a favorite place for developers, the advantages of working with bright minds, and how the little things add up for developers</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4311Pmyst3JvB-yLtxIPwQ.png" /><figcaption>Team @Deutsche Telekom Digital Labs</figcaption></figure><p><strong><em>When we ask our developers “why DTDL is a favorite place for you?”</em>,</strong></p><p><em>we usually get the following response:</em></p><blockquote><strong>“New problems to solve every day with a focus on technology-oriented solutions to better the lives of customers. There is never a dull moment at work!”</strong></blockquote><blockquote><strong>“Opportunities to try out new roles, work in a global environment, and the best part is that the learning never stops here”</strong></blockquote><blockquote><strong>“ The chance to watch a Champions League match live in Munich as a reward for my first ever delivery was the most amazing experience ever”</strong></blockquote><blockquote><strong>“Problems that we are trying to solve are complex. Hence, the complexity of the landscape acts as the best way to test my potential and improve my ability to try new things”</strong></blockquote><p><em>Our purpose at DT Digital Labs is to help customers of Telekom go digital &amp; hence gain trust. </em>That is what we have been doing in the last two years.<em> Our single code base now supports 10 countries. Our centrally developed self-service application boasts of a 56% customer penetration rate. Our microservice architecture contrives multitenancy, multi-lingual, multi-currency, and featured flag based development. Some numbers at a glance</em></p><p>· 15M API requests per day</p><p>· 2000 TPS on internal platforms</p><p>· 10B+ searchable documents</p><p>· 220M campaign queries a day</p><p>· 125M events generated per day.</p><p><em>A best in class e-commerce experience, single Telekom app for self-care, omnichannel TV experience (App, web, STB), and improving customer’s life by providing the most reliable Wi-Fi experience, are just some of the interesting problems our team is trying to solve, even as we speak.</em> <em>But this is just the tip of the iceberg &amp; there is so much more to dream, build &amp; achieve.</em></p><p><strong><em>So what’s makes us such a vibrant company when numerous other companies are doing similar stuff?</em></strong></p><blockquote>1. <strong><em>Customer Obsession</em></strong></blockquote><blockquote>2. <strong><em>Developer’s — First and Foremost</em></strong></blockquote><blockquote><strong><em>3.</em></strong> <strong><em>Empathy &amp; Compassion</em></strong></blockquote><p>Customer obsession has been a core driver since inception &amp; we are driven by the purpose of transforming people’s lives &amp; changing the way they not only interact with us a Telco, but the way they access information, healthcare, education, entertainment, and lifestyle in general entertainment, and lifestyle in general.</p><p>Some habits we live &amp; breathe by which make us a customer-centric organization:</p><ul><li>We align every employee to be part of the customer journey &amp; success</li><li>We put customers at the heart of every decision we make</li><li>We value the quality of the product over quantity of code check-ins</li><li>Decisions are driven by data insights and customer feedback</li><li>We analyze customer data repeatedly and strive to continuously improve the customer experience.</li></ul><p>That’s what it means to be customer-obsessed. If you ever settle, you’re doing it wrong.</p><p><strong><em>So how do we breathe life into this term customer obsession?</em></strong></p><p><strong>Data, Data &amp; More Data-Driven Insights — Customer Journey Insights Dashboard</strong></p><p>This philosophy is based on tracking the customer insights through well informative dashboards, customer feedbacks &amp; surveys, regularly monitoring the comments over the app store, and customer-focused group experiments. Our customer platforms generate a massive amount of data that is logged and analyzed to deliver an excellent customer experience as well as improving the quality. Constantly improving the experience for customers is a never-ending goal for us.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gJaWRNvsftt9OqMPH21uzw.png" /><figcaption>OneApp data visualization</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WhndQiEtUe6dq09PG-0PYg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JIA69XShM164Xo0CN_NyZA.png" /><figcaption>OneShop heatmap of user clicks and OneApp T-mobile CZ play store reviews</figcaption></figure><h3>Developers — First and Foremost</h3><p>Depending on the organization’s size and needs, being developer-focused can mean different things. In this extraordinary situation(COVID), gone are the days that developers are attracted to perks like vending machines, video games, free organic juices, pool tables, etc. Developers work best in a loose and non-corporate environment. They look forward to the organizations that provide overall growth — professionally and personally.</p><p>Being at the heart of Deutsche Telekom, we encourage a start-up culture with a huge focus on developers. Making developers feel special is key to DT Digital Labs’ success. We believe that when a developer gets to work with us, it should feel delightful<em>.</em></p><p><strong><em>Why we think, We are developer-focused?</em></strong></p><ul><li>We are heavily relying on Open Source technologies. We have developed a “<em>default to open source</em>” mentality to every project we work on. It does allow developers to explore solutions and try out new things. A great example of it using the community version of Keycloak (Identity and Access Management) &amp; Sylius (e-commerce sales catalog) internally and customizing to scale up for our business needs. <em>D</em>evelopers always have the option to try various alternatives, pick the one that’s going to work, and modify this with the customized needs. It allows them to be flexible, agile, able to start quickly, and inexpensively.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3qFLiGLxJwKbxhPbpnyPtg.png" /><figcaption>Technologies we eat, sleep, breathe…</figcaption></figure><ul><li>There are several real examples of developer’s initiatives that are directed into full-fledged products. Their intention wasn’t only to just build something that “just worked”. But they have built something that solved the problems they faced as developers. OneView (Real-time monitoring and tracking), Page Builder, Campaign Management, Data Lake, and numerous platform (currently live) examples that are initiated by the developers.</li><li>In DTDL, developers perceive an opportunity to write the first line of code. We have so many platforms to build. Me being a engineering leader can vouch that, this is such a delightful feeling when you start writing code from scratch and turn your imagination into reality. Developers get a chance to experiment with different ideas and technologies. We encourage our developers to take complete ownership and care about the product’s success.</li><li>We focus a lot on the re-usability of internal components and libraries. DTDL has a kind of Pseudo internal open source contribution culture. Anyone can publish a new set of the code or change the code of the existing platform (with a code review process). Many platforms e.g. CMS, sales catalog, campaign, etc are commonly used across multiple projects.</li><li>Providing the right tools and learning opportunities is a must to have for the growth of the developers. DTDL is committed to providing the ultimate learning environment. Every developer has access to Percipio &amp; Coursera licenses. Developers nominate themselves for the monthly tech sessions to promote a learning culture. We have rewarded our top learners with Nano degree programs</li></ul><h3>Empathy &amp; Compassion</h3><p>Making a developer feel like he is part of the family from day one, is what makes this a special place.</p><p>It is all about the emotions &amp; connections that we forge together as a team. It is not so much about the ‘unrestricted leave policy’ but an understanding manager who says ‘Don’t worry! I got your back’. It is about a team that pitches in to pick up work when you need to be at home to celebrate Halloween with your kid. Wherever there is a necessity, the whole team will jump in to help extinguish it. That’s what makes this team special.</p><p><strong><em>But how do we build such a culture of care &amp; compassion?</em></strong></p><ul><li>We pause, reflect, connect and listen — Be it the head of a function, a colleague, or even the People Team, everyone makes the effort to listen, reflect &amp; we never refrain from asking questions or getting feedback. Be it coffee connects with leaders or chit chat sessions with leads &amp; peers, everyone makes the time to invest in relationships &amp; people. We have succeeded to maneuver the corona situation &amp; virtual ways of working &amp; have ensured people take out the time for a Teams call with colleagues &amp; peers.</li><li>We empathize — whether it is adapting to new ways of working, introducing policies that are more aligned to the current needs of the team, or asking the right questions to ensure we understand what the team is feeling. The year 2020 has tested us on how empathetic we are &amp; whether it is an open leave policy, better insurance coverage to support the medical needs amidst the corona, remote working, or setting up a home office, we tried to always help our team feel safe, secure &amp; taken care of by the organization.</li><li>Flexibility &amp; Respect — In today’s pandemic times this is even more important. We make time to talk 1:1 about work issues, understand the need for flexible working hours and time off for personal, family, or medical issues &amp; respect personal working styles.</li></ul><p><strong>Other little things we do that adds up for developers</strong></p><ul><li>Developers own the code and we count on them. We encourage rewards every month, quarter, and year. We do monthly spot awards, quarterly top performer awards, a wall of fame to recognize the fantastic work done. In a recent example, for recognition of the achievement, we allowed the team to watch the champions league live match in Munich.</li><li>We beget an open and non-hierarchal culture. We boost our developers to have a voice when a system or process is not working. Anyone can reach out to the leaders courageously.</li><li>We celebrate failure &amp; encourage people to share the stories of tech failures &amp; errors, with the intent of learning from each other on how to not to repeat the same.</li></ul><p>We are still a growing team and won’t shy in saying that, we are not perfect. However, we try to do every possible step to make our developers and customers happy. We won’t stop till Deutsche Telekom goes digital. #wewontstop</p><blockquote>Stay tuned for some interesting reads coming in this space :)</blockquote><p>References: https://subvert.substack.com/p/stripe-building-a-developer-cult</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=22ccd467801e" width="1" height="1" alt=""><hr><p><a href="https://blog.dtdl.in/deutsche-telekom-digital-labs-building-a-customer-obsessed-developer-cult-22ccd467801e">Deutsche Telekom Digital Labs: Building a Customer Obsessed Developer Cult</a> was originally published in <a href="https://blog.dtdl.in/">Deutsche Telekom Digital Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>