<?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 Michael Bailey on Medium]]></title>
        <description><![CDATA[Stories by Michael Bailey on Medium]]></description>
        <link>https://medium.com/@padihamtown?source=rss-58fbc5f9382e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*5u5Agqtb8SUxiQanf1rQGg.png</url>
            <title>Stories by Michael Bailey on Medium</title>
            <link>https://medium.com/@padihamtown?source=rss-58fbc5f9382e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 09:16:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@padihamtown/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[How we fixed our workflow problems with Asana]]></title>
            <link>https://medium.com/@padihamtown/how-we-fixed-our-workflow-problems-with-asana-7e464f67f222?source=rss-58fbc5f9382e------2</link>
            <guid isPermaLink="false">https://medium.com/p/7e464f67f222</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[students-union]]></category>
            <category><![CDATA[asana]]></category>
            <category><![CDATA[charity]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Michael Bailey]]></dc:creator>
            <pubDate>Thu, 27 Jun 2019 13:09:04 GMT</pubDate>
            <atom:updated>2019-06-27T18:17:40.710Z</atom:updated>
            <content:encoded><![CDATA[<p>If you’ve ever had the joy of working in a Students’ Union you’ll know that they’re not always the bastion of professionalism you see in the corporate world. And, while having the shackles released is an absolute joy, it can also result in absolute carnage. Processes break down, deadlines get missed and workloads get out of hand. Eventually, it’s time to take a step back and say enough is enough.</p><h3>Taking a Condor Moment</h3><p>I knew the way teams requested support from my department wasn’t working. From staff consistently appearing at my desk to discuss the latest design drafts through to dreaded corridor conversations — look Dave, I’m sure that boosted Facebook post is really important to you but I’m going to instantly forget what you just said because right I’ve got a million other things going on.</p><p>So I started to look at what processes we had in place to try and get to the root of the problem and discovered a number of flaws:</p><ol><li>Work was coming in through a number of different channels: meeting actions, emails, desk conversations, phone calls, paper forms and more.</li><li>There was no centralised location for work requests. Simply put, I had no way of understanding our workload, capacity or prioritisation. Not only did I waste time figuring out where we were with projects but it became increasingly difficult to justify missed deadlines to senior management.</li><li>Requests had no consistency in their format and often missed key information.</li><li>When given the option on what collateral was required to support their request, teams would literally select everything no matter the size of the project.</li></ol><p>Now that I had an idea of the issues we were facing I should have set out the goals for a new system and used that to drive my market research. Instead, I floundered for 18 months, drowning in work while testing a whole host of potential solutions.</p><h3>The Art of Drifting Aimlessly</h3><p>I’ll cut to the chase and reel off the different tools we attempted to use and their shortcomings:</p><p>Excel — We built our own tracking spreadsheet which quickly became unmanageable. We simply had too wide a range of projects with to many intricate tasks to contain on a single spreadsheet.</p><p>Trello — We dipped our toe in the water with a Kanban system and stuck with it for our design work for a considerable amount of time. It worked when managing tasks for our part-time staff but it didn’t fix a number of the problems we identified.</p><p>WorkStraight — This was our first attempt at using an actual ticket based system. It half worked but felt like we were forcing it to be something it wasn’t. Plus the design team hated it.</p><p>A Massive Whiteboard — In my search, I even went as far as using a huge 4m wide whiteboard and accompanying magnetic strips in an effort to create a tactile Kanban board. It looked nice but was ultimately a bit shit.</p><p>With no clear solution in sight, I stumbled across Asana while researching companies who had successfully rebranded (a topic for another day) and knew I was finally on to something big.</p><h3>Actual Market Research</h3><p>At first glance, it had everything I wanted in a product, with solutions to the problems I had identified back in 2015. But, the toil of the past year had taught me I needed to be sure, so I drew up a shortlist of candidates and a plan for beta testing with the team.</p><p>In the mix along with Asana were Wrike, Jira and Podio. Jira felt too big and enterprise focused for the size of our small team while I struggled to love the UI of Podio (this is something I’d be using every day after all).</p><p>Finally, it came down to Wrike. There really isn’t much to distinguish the two products and it was simply a case of Asana’s trial offering us the ability to onboard a large enough sample to fully test it across multiple teams which saw it come out on top.</p><h3>Onboarding, Prototyping and Integrations</h3><p>I was now happy to move forward to large scale testing and worked closely with our design team to build out project templates that would work for them. Alongside this, we crafted a more robust version of our old WorkStraight system. The trickiest part was getting our Google Form to fire new requests into our ‘Marketing Requests’ project but once we’d solved that we knew we were ready to bring external teams into the fold.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7BA5lB0EAQlm2Z_2b30rHA.png" /><figcaption>Our Marketing Request project. We’re big Rick and Morty fans in the office…</figcaption></figure><p>They were more than happy to give feedback and after some discussions, we expanded the range of information required in our request form while also adding descriptor text to headers and removing questions that just added unnecessary complexity. We now had a firm solution that allowed all teams across the organisation to submit requests for support in an easy to use format with the added bonus that it was accessible on any web browser.</p><p>Having all our requests pulled into one location made it incredibly easy to understand our workload, priorities and team capacity — a huge step forward. We also created a general user account that was locked down to commenting and shared this with the wider staff team so that they could check in on their requests and understand the different tasks we were working across.</p><p>While smaller requests could be handled on a case by case basis, we quickly understood that we would need to create individual projects for our larger campaigns such as Freshers’ Festival, Summer Ball and our annual Elections.</p><p>Pulling these out into their own distinct areas allowed us to be far more granular in our planning, with sections built out to cover key areas such as website launches, video development, digital assets, print orders, budgets and more. It was a small tweak but one that gave me the oversight I need as a senior manager.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JWVQeoBVa79fTuXJfc3ghA.png" /><figcaption>A snapshot of our Summer Ball 2019 project area.</figcaption></figure><h3>Reflect, Learn and Move Forward</h3><p>Along the way, I’ve learned a lot about project management and how the principles behind it can be applied to different business functions. Here are a few of my top tips:</p><ol><li>Don’t just drift hoping a solution will magically appear. Once you’ve identified an issue explore the options around you and reach out to your networks for help and support. Had I done that back in early 2016 I would have potentially accelerated this process by 18 months.</li><li>Take the time to understand the needs of your team and the wider organisation. It’s pointless rolling out a system that is great for you but a nightmare for your colleagues.</li><li>Ask for feedback! Get it at every step and don’t be afraid to iterate and change things up. I approached this process wanting to solve marketing request issues and through feedback, we’ve expanded it to include our editorial and email calendars, new employee inductions and meeting agendas.</li><li>When you have a solution, take the time to explain it to the wider staff team and explain why you’re making a change. I presented Asana at an all-staff meeting, sent organisation wide emails and invited people to beta test so they understood the journey. Now everyone understands that if they want marketing support they log a ticket through Asana.</li></ol><h3>Next Steps on Our Journey</h3><p>The success of the rollout has allowed me to understand how utilising this type of software could have positive impacts across the wider staff team at Royal Holloway Students’ Union. For example, I’ve started to take the first steps on exploring how we can use Zapier to update Google Sheets for our Advertising and Media Sales team when tasks are added/amended on a project while our Trading Services team have moved their event calendar onto Asana so we get instant updates when changes are made.</p><p>Longer term, there’s the potential to move all major projects online, improving oversight, collaboration and efficiency on an organisation wide scale. These type of changes excite me because I’m a massive geek in that regard but before any of that, I’ll be sure to reach out to colleagues about the challenges they face in delivering projects, identify their issues and attempt to understand how we can apply what I learned during this process to find a solution.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7e464f67f222" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>