<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Productivity on Rakesh Mothukuri</title><link>https://rakeshmothukuri.dev/tags/productivity/</link><description>Recent content in Productivity on Rakesh Mothukuri</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026</copyright><lastBuildDate>Sat, 28 Mar 2026 22:00:00 +0100</lastBuildDate><atom:link href="https://rakeshmothukuri.dev/tags/productivity/index.xml" rel="self" type="application/rss+xml"/><item><title>Jira Might Be Slowing Us Down</title><link>https://rakeshmothukuri.dev/posts/jira-might-be-slowing-us-down/</link><pubDate>Sat, 28 Mar 2026 22:00:00 +0100</pubDate><guid>https://rakeshmothukuri.dev/posts/jira-might-be-slowing-us-down/</guid><description>&lt;p&gt;I&amp;rsquo;ve been noticing this for a few months now.&lt;/p&gt;
&lt;p&gt;Jira, at least the way we use it today, often feels like it slows things down more than it helps. Not because it&amp;rsquo;s a bad tool, but because it&amp;rsquo;s optimised for a way of working that may no longer match how execution actually happens.&lt;/p&gt;
&lt;p&gt;In larger organisations, Jira serves clear purposes: visibility, alignment, accountability, and coordination. Those are real constraints. But that doesn&amp;rsquo;t automatically mean, given how things have evolved, that it&amp;rsquo;s still the right default approach.&lt;/p&gt;</description></item></channel></rss>