<?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 Darryl S on Medium]]></title>
        <description><![CDATA[Stories by Darryl S on Medium]]></description>
        <link>https://medium.com/@darryl-snow?source=rss-a88d4c393445------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Stories by Darryl S on Medium</title>
            <link>https://medium.com/@darryl-snow?source=rss-a88d4c393445------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 10:28:37 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@darryl-snow/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[Learnings for Agencies and Freelancers Working on Projects for Large Organizations]]></title>
            <link>https://darryl-snow.medium.com/learnings-for-agencies-and-freelancers-working-on-projects-for-large-organizations-9bc2232f98f2?source=rss-a88d4c393445------2</link>
            <guid isPermaLink="false">https://medium.com/p/9bc2232f98f2</guid>
            <dc:creator><![CDATA[Darryl S]]></dc:creator>
            <pubDate>Sat, 01 Jun 2019 01:53:36 GMT</pubDate>
            <atom:updated>2019-06-01T01:53:36.811Z</atom:updated>
            <content:encoded><![CDATA[<ul><li><strong>Stakeholder management</strong> is key — quickly identify the decision makers and the people you need to keep happy; if you don’t think there are decision makers, then explain how important it is for you and push your main point of contact to assign people.</li><li>Highlight that you understand the problem and that <strong>you are focused on outcomes</strong> — anchor conversations around these outcomes.</li><li>Be part of the team, but don’t get buried — stay focused on the desired outcomes and the <strong>strategy</strong> to achieve them.</li><li>Be open and honest — push regular updates and don’t wait to be asked, <strong>stick to the facts</strong>, don’t insinuate, don’t speculate, <strong>ask questions</strong>.</li><li>Be <strong>loud and clear</strong> about <em>your</em> process — they are not hiring you to follow <em>their</em> process — if their process worked, they wouldn’t need you; share the way you work and why; this will provide reassurance and demonstrates your value.</li><li>Broadcast your achievements — provide regular <em>structured</em> <strong>demos</strong>.</li><li>Have <strong>empathy</strong> — the people you work with are bound by their internal processes — they will likely have their own duties, their own reporting, responsibility on budgets, timelines, and approvals — they face a huge challenge too. Try to identify and <strong>align goals</strong> with your key stakeholders.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9bc2232f98f2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Advice for Anyone in a Large Organization Hiring Someone from Outside]]></title>
            <link>https://darryl-snow.medium.com/advice-for-anyone-in-a-large-organization-hiring-someone-from-outside-56f4d7f4afdc?source=rss-a88d4c393445------2</link>
            <guid isPermaLink="false">https://medium.com/p/56f4d7f4afdc</guid>
            <dc:creator><![CDATA[Darryl S]]></dc:creator>
            <pubDate>Wed, 29 May 2019 00:13:48 GMT</pubDate>
            <atom:updated>2019-05-29T00:13:48.166Z</atom:updated>
            <content:encoded><![CDATA[<ul><li>Provide lots of support and transparency with the quirky organizational processes</li><li>Give clear strategic direction, set expectations</li><li>Teach them the process, but ensure they have the flexibility to achieve your desired outcomes without being burdened by the process</li><li>Identify and evangelize the set of expertise that they bring to help garner support for them</li><li>Ask them for advice on specific issues</li><li>Recognise agile leadership <a href="https://medium.com/@darryl.snow/agile-leadership-patterns-39e0dab8f8fb">patterns</a> and <a href="https://medium.com/@darryl.snow/agile-leadership-anti-patterns-42a0a4c88a7a">anti-patterns</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=56f4d7f4afdc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Advice for Anyone Joining a Large Organizations from an Agency or Freelance Background]]></title>
            <link>https://darryl-snow.medium.com/advice-for-anyone-joining-a-large-organizations-from-an-agency-or-freelance-background-37f318ffeda0?source=rss-a88d4c393445------2</link>
            <guid isPermaLink="false">https://medium.com/p/37f318ffeda0</guid>
            <dc:creator><![CDATA[Darryl S]]></dc:creator>
            <pubDate>Tue, 28 May 2019 00:28:16 GMT</pubDate>
            <atom:updated>2020-03-26T14:37:33.946Z</atom:updated>
            <content:encoded><![CDATA[<ul><li>Network!</li><li>Be prepared for culture shift</li><li>Agency people are generally more self-starter, more hungry, not so comfortable, have a broader skill set and experience — try to identify the knowledge and skills boundaries of your new team mates quickly</li><li>Talk loudly and often about even your minor successes — what seems to you as something small or mundane to you might be inspiring to someone else</li><li>Try to identify key senior stakeholders and cultivate strong relationships quickly — show them what you can do — you will need their help at some point</li><li>Stand your ground and loudly demonstrate your expertise — make it known to your line managers that you need help with the processes so that you don’t get bogged down and can spend your time better putting to good use the skills you bring</li><li>Lean heavily on those with the knowledge rather than trying to spend time learning it yourself — focus just on what you need to know to do your job and pull in others whenever needed, focus on outcomes</li><li>Reject or dismiss yourself from meetings to which you won’t bring value</li><li>Identify and deflect grunt work</li><li>Prioritize or, better yet, entirely ignore emails</li><li>Maintain courtesy</li><li>Stay positive, don’t take anything personally</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=37f318ffeda0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What I learned Working in a Bank]]></title>
            <link>https://darryl-snow.medium.com/what-i-learned-working-in-a-bank-940024d6361e?source=rss-a88d4c393445------2</link>
            <guid isPermaLink="false">https://medium.com/p/940024d6361e</guid>
            <dc:creator><![CDATA[Darryl S]]></dc:creator>
            <pubDate>Sun, 26 May 2019 23:59:12 GMT</pubDate>
            <atom:updated>2019-05-26T23:59:12.278Z</atom:updated>
            <content:encoded><![CDATA[<p>I already knew large organizations had challenges like communication silos and budget cycles. I already knew documentation was important for distributed teams working on large complex systems, and that there wouldn’t be any. I already knew that automated tests would be lacking. I already knew the teams I would be working with would be less experienced with agile processes. Some of the things that were beyond my expectations were:</p><ul><li>Large organizations are super chaotic</li><li><a href="https://en.wikipedia.org/wiki/Conway%27s_law">Conways law</a> rings true</li><li>Networking is really extremely important!</li><li>I should celebrate every small win</li><li>I should seek and cultivate strategic sponsors</li><li>I need to work on senior stakeholder management</li><li>Internal costs are always higher than any vendor cost, no matter the scope</li><li>Legacy people are a much bigger challenge than legacy systems</li><li>Banks are extremely risk averse to the point of paranoia — vendors should be advised to take this into account</li><li>Outsiders should empathize with the challenges faced by the people in large organizations, especially when it comes to budgeting and reporting</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=940024d6361e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Working as a Product Owner in a Bank: What Didn’t Go Well]]></title>
            <link>https://darryl-snow.medium.com/working-as-a-product-owner-in-a-bank-what-didnt-go-well-e8dac37b94cb?source=rss-a88d4c393445------2</link>
            <guid isPermaLink="false">https://medium.com/p/e8dac37b94cb</guid>
            <dc:creator><![CDATA[Darryl S]]></dc:creator>
            <pubDate>Sat, 25 May 2019 03:29:36 GMT</pubDate>
            <atom:updated>2020-03-26T14:36:05.444Z</atom:updated>
            <content:encoded><![CDATA[<ul><li>No products launched! In almost 2 years!</li><li>Communication, especially within the product teams, could have been improved</li><li>No product or feature could be adequately tested, in <em>any</em> test environment</li><li>Teams ultimately fell back to waterfall practices when timelines and budgets went into the red, mostly because of the testing difficulties</li><li>All deadlines were missed</li><li>Senior stakeholder management could have been handled better — I didn’t push back enough when pushed for arbitrary time and dollar-cost estimates</li><li>Velocity tracking was not possible, which made planning and forecasting close to impossible</li><li>I had limited time for product management duties, just as my scrum masters had little time to support the scrum process — we had too much admin and paperwork to handle</li><li>I rarely got the help I asked for, and escalations were usually ineffective</li><li>Many stakeholders were unable to grasp basic concepts, making decisions and approvals difficult, sometimes impossible</li><li>I wasted time learning processes rather than ways to work around them to achieve outcomes</li><li>I wasted too much time in meetings</li><li>I wasted time on forecasts and time sheets</li><li>I didn’t cope with the stress as well as I used to</li><li>I took things too personally</li><li>I complained too much and should have offered solutions more than problems</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e8dac37b94cb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Working as a Product Owner in a Bank: What Went Well]]></title>
            <link>https://darryl-snow.medium.com/working-as-a-product-owner-in-a-bank-what-went-well-39c5954515be?source=rss-a88d4c393445------2</link>
            <guid isPermaLink="false">https://medium.com/p/39c5954515be</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[banking]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Darryl S]]></dc:creator>
            <pubDate>Thu, 23 May 2019 12:59:43 GMT</pubDate>
            <atom:updated>2020-03-26T14:33:06.789Z</atom:updated>
            <content:encoded><![CDATA[<ul><li>I set out clear product vision and aligned it with company strategy</li><li>I got a <em>lot</em> better at stakeholder management</li><li>I set out clear roadmaps and got good alignment from various stakeholders</li><li>I set a strong tone and in instilled confidence among stakeholders</li><li>I learned a lot about banking, especially how credit cards and payments work, as well as the underlying systems</li><li>I was able to mould some processes towards agile delivery —actually building, testing <em>and</em> reviewing <em>during</em> sprints was a big win</li><li>I inspired some changes towards agile in other teams</li><li>I shared a lot of skills among Devs and POs around user stories, story mapping, backlog management, agile ceremonies, as well as the use of tools like JIRA and Confluence</li><li>I framed conversations about risk around specific user stories</li><li>I tracked towards milestones well</li><li>I kept all my projects on budget by prioritizing resources</li><li>I found creative ways to workaround communication issues using mobile apps</li><li>I made good impressions/friendships</li><li>I sparked a few good ideas</li><li>I managed my backlogs well… even if they weren’t fully used</li><li>I asked for help a lot</li><li>I discovered the ultimate bestest 2-step process to handle emails: 1) I set a rule in Outlook to automatically mark all incoming mails as read and move them to the junk folder, and 2) I literally had my out-of-office auto-reply on 24/7, asking people to call me or comment on user stories; this was a <strong>huge</strong> help</li><li>I remained courteous and helpful, somehow</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=39c5954515be" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Challenges Faced Working in a Bank: #12 Culture Misfit]]></title>
            <link>https://darryl-snow.medium.com/challenges-faced-working-in-a-bank-12-culture-misfit-892f6a61ec53?source=rss-a88d4c393445------2</link>
            <guid isPermaLink="false">https://medium.com/p/892f6a61ec53</guid>
            <category><![CDATA[banking]]></category>
            <category><![CDATA[diversity]]></category>
            <dc:creator><![CDATA[Darryl S]]></dc:creator>
            <pubDate>Wed, 22 May 2019 11:25:31 GMT</pubDate>
            <atom:updated>2020-03-26T14:28:11.301Z</atom:updated>
            <content:encoded><![CDATA[<p>This is a big one. It was entirely expected, but I overestimated my ability to adapt and fit in.</p><p>Everyone I met working at the bank had always worked for a bank. They had only ever worked with people who had always worked for a bank. All their friends worked in banks, and had only ever worked in banks. Their families, all bankers. Similar professional and professional-social backgrounds. They’re bank people. They use “bank” as a verb in regular conversation…</p><p>This meant that a lot of conversations were framed by assumptions on someone’s knowledge and experience — both of which I did not have. A lot of the behaviors and thought processes I observed seemed quite alien. I became convinced that humanity was approaching a zeitgeist after which bank people and other people will no longer be able to inter-breed; and, I must confess, the longer I stayed at the bank the harder I clung to this idea.</p><p>I also found it very male dominated and surprisingly culturally conformative. A lot of men from the same cultural background, and a lot of bravado and swaggering. There were even some clear racial/cultural silos. Having been accustomed to working with a more diverse and easily blended mix of genders, ethnicities and cultures, this often made me feel more uncomfortable. I think I eventually learned to cope quite well.</p><p>Perhaps it speaks more to my naivety, inexperience, or lack of maturity, but it genuinely felt like the company dynamics created a culture of suspicion and blame. In agencies we always joked about the clients, but at least we were always aligned behind the same goal. At the bank I faced a lot of back-channeling and concealed objectives, even from my closest team members.</p><p>What really got me down, however, was the endless negativity. It was when I noticed the attitudes of people I interacted with slowly infecting my own that I decided to leave. Most times when I asked for help, I would be ignored, dismissed, met with complaints and arguments, or would be deferred to someone else. I always tried to be courteous in replying to messages, responding to requests for help, and being punctual to meetings that I’d accepted. However, it was very rare that any of this was reciprocated. People seemed adept at finding problems and reasons why things couldn’t be done, and no one willing to offer solutions, even suggestions, or accept responsibility. This was extremely frustrating as a product manager, one who essentially coordinates people and work towards a goal, and I probably took things too personally. It was difficult not to.</p><p>I think it boils down to everyone being, or at least feeling, <em>too busy</em>. I get that everyone is busy, but I do believe most people are probably busy with the wrong things. For instance, the majority of meetings don’t <em>need</em> to last so long and don’t <em>need</em> all 10 people. We don’t <em>need</em> to attend every meeting. We all follow the long and overcomplicated processes. And then there’s the emails. Emailing isn’t work. In agencies and consultancies, everyone is always super busy, and yet mostly very positive and supportive in my experience. This is probably a result of smaller organizations and smaller teams being better positioned to offer mutual support; like how a family may feel more supportive than a national government. In my experience at least, the successful people who I’ve met in agencies have been excellent at cultivating, supporting, and motivating their teams; successful people I met in the bank were often those who would likely shank someone on their first day in prison.</p><p><strong>Conclusion</strong>: Large organizations are less able to support people than smaller ones, and it takes a mature and positive, even ruthless, attitude to be successful. Before joining a large organization, I would try to vet the organization and team culture. I would consider the background and experience of the team members and whether mine might be harmonious or conflicting. I will certainly consider how to assess whether my personal and professional values are aligned with any company I might join in future. I will also endeavour to control my emotions and remain calm and positive in the face of any challenges.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=892f6a61ec53" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Challenges Faced Working in a Bank: #11 Misdirection of Resources]]></title>
            <link>https://darryl-snow.medium.com/challenges-faced-working-in-a-bank-11-misdirection-of-resources-4e3fd3d472c8?source=rss-a88d4c393445------2</link>
            <guid isPermaLink="false">https://medium.com/p/4e3fd3d472c8</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[banking]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Darryl S]]></dc:creator>
            <pubDate>Tue, 21 May 2019 11:51:40 GMT</pubDate>
            <atom:updated>2020-03-26T14:20:58.885Z</atom:updated>
            <content:encoded><![CDATA[<p>Effective teams have the right people in the right places. During my time at the bank, I often encountered situations where this clearly wasn’t the case. Some comical examples:</p><h4>The Wrong People in the Right Place</h4><ul><li>Senior digital banking leads who didn’t know how to use their own smartphones (the basics, like logging in, switching apps, and typing stuff… it was like being in a bad sitcom)</li><li>Senior digital banking leads who had to ask me what an API was, and if the bank used any, so that they could better respond to media requests</li></ul><p>When you are relying on such people for strategic decisions and guidance, it’s extremely unsettling to find out they are not at all equipped, to say the least, and makes communication all the more difficult.</p><h4>The Right People in the Wrong Place</h4><ul><li>Me, a designer/developer/product manager, negotiating with a vendor an 85-page multi-million dollar legal contract (I’d only gone and forgotten to get my darn law degree… <strong>doh</strong>!)</li><li>A junior front-end JavaScript developer fixing bugs in someone else’s untested and undocumented Java services for handling credit card data</li><li>The same junior front-end developer preparing long and over-complicated reports and documents to support the change control process (in another language, I might add, the poor trooper)</li><li>“Scrum masters” managing team payroll</li></ul><p>In each of these situations, there was no clear way around it — nobody else was available to call on. When you task people with things they’re not equipped to deal with, or not interested in, their enthusiasm wanes and patience wears thin. When we had supply chain management and legal and sourcing experts, I felt resentful that I was spending hours each day reading through legalese and reviewing comments. I could have better spent those hours grooming a backlog or reviewing analytics data or any number of other things that I was both interested in and good at. This led to a great amount of stress. Placing someone out of their comfort zone to challenge them to learn new things is a good idea, but only when you feel they are at least prepared for it and eager to learn. In my case, I clearly wasn’t prepared, and legal negotiations are unlikely to ever be a career focus of mine. I was put in that situation only because someone, <em>anyone</em>, was needed to get the work done. This was the same for the scrum masters and the developers I worked with, and is only one example of many.</p><p>This was a big motivator for my decision to leave the bank — I wasn’t spending my time doing what I wanted to be doing, or learning what I wanted to learn. I could have spoken up more to my line managers before resigning, but I’m not sure how effective it would have been, either in the short or long term.</p><p><strong>Conclusion</strong>: Key senior roles need to be filled with the people who are best equipped to drive strategy. People who are not equipped should be moved somewhere they are better suited, or trained until they are ready to take on the role. Large organizations don’t always have all the resources to get the job done — we can’t always assume that the larger the organization the more resources they have. Sometimes, <em>anyone</em> just has to roll up their sleeves to do the grunt work. <em>Sometimes</em>, it’s a learning opportunity. <em>Most</em> of the time, it’s not, so just try and make sure you’re not the someone.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4e3fd3d472c8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Challenges Faced Working in a Bank: #10 Legacy People & the Illusion of Agile]]></title>
            <link>https://darryl-snow.medium.com/challenges-faced-working-in-a-bank-10-legacy-people-the-illusion-of-agile-83af93d5db8e?source=rss-a88d4c393445------2</link>
            <guid isPermaLink="false">https://medium.com/p/83af93d5db8e</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[banking]]></category>
            <dc:creator><![CDATA[Darryl S]]></dc:creator>
            <pubDate>Mon, 20 May 2019 04:10:03 GMT</pubDate>
            <atom:updated>2020-03-26T14:16:11.378Z</atom:updated>
            <content:encoded><![CDATA[<p>I remember before I started at the bank people told me I would be struggling with legacy systems. I didn’t find the <em>systems</em> to be such a problem though… Ultimately, it’s still just data tables manipulated by functions that are exposed via APIs. Sure, a lot of those APIs are SOAP and, yeah, there’s a lot of XML flying around, and, admittedly, a lot of the fields were ambiguous, overlapping, or redundant. It’s likely there have been lots of customizations that haven’t been documented, spaghetti code, no unit or integration tests. But there are always developers who have worked on it for years and who understand how it all works, or who at least have experience on similar systems and can work it out.</p><p>Software and hardware problems are always surmountable. It’s the <em>wetware</em> that I struggled with — the <em>people</em> who have spent their whole careers in the bank, or in other banks, always doing things the same way. People who have only ever worked with <em>other</em> people who have spent their whole careers in banking. People who have grown accustomed to fat salaries and consistent bonuses, regardless of merit. People who see their role as demanding cost estimates and scope documents and fixed timelines. People who have no experience in business agility and no incentive to do anything differently let alone learn. Some of these people were very senior and, most obfuscatory, others had job titles like “Scrum Master” or “Product Owner”. Legacy mindsets. Legacy people all.</p><p>In retrospect, I should have known all this and been prepared. I never stopped driving and evangelizing agile processes, beating that drum… but I wish I’d been more accepting, more empathetic, bringing more positivity rather than complaints. I could have pushed back on demands for magic numbers from senior stakeholders, instead better guiding them to align on desired outcomes. I certainly felt less empowered and less confident as a reportee compared to being an outside consultant. I could have also better framed my opinions on the way work was being done, using familiar and digestible materials like the scrum guide to help find solutions to specific obstacles that people on my team were facing. I could have encouraged them to take the initiative by themselves. <a href="https://medium.com/@darryl.snow/top-down-agile-78b64b962d4">Agile transformation</a> can be neither top-down nor bottom-up — it must be both.</p><p><strong>Conclusion</strong>: Large organizations should indeed hire strong change agents and encourage process and mindset change, perhaps through merit-based incentives (rather than de-facto bonuses). They should hire people from diverse backgrounds and experiences, especially those from other industries, or otherwise outsource their digital product work to agencies. As a lone <a href="https://medium.com/@darryl.snow/making-a-difference-slowly-db7d355e8adc">change agent</a> myself, I should have been more accepting, more patient, more empathetic, and driving more positive change rather than complaining so much.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=83af93d5db8e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Challenges Faced Working in a Bank: #9 Email & Distributed Teams]]></title>
            <link>https://darryl-snow.medium.com/challenges-faced-working-in-a-bank-9-email-distributed-teams-94395f2707df?source=rss-a88d4c393445------2</link>
            <guid isPermaLink="false">https://medium.com/p/94395f2707df</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[banking]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Darryl S]]></dc:creator>
            <pubDate>Sun, 19 May 2019 03:01:46 GMT</pubDate>
            <atom:updated>2020-03-26T14:08:31.209Z</atom:updated>
            <content:encoded><![CDATA[<p>This is another obvious one. In any large organization, you’re likely to be working with people based out of different countries and timezones. Timezones are easier to manage — people can just adjust their working hours. A major challenge this posed at the bank was in the lack of good tools — screen sharing and video conferencing was almost impossible, file sharing and chatting was cumbersome, and email was king. Even our audio conferencing was unreliable. Transferring documentation files, decks, and UI mockups, or conducting product review meetings, backlog refinement meetings and planning meetings — these were all needlessly painful and seriously inhibited productivity. On the plus side, JIRA and Confluence are super useful collaboration tools, but at times I felt like the only person in the bank that was using them. I had to get quite creative, using WeChat and Whatsapp video calls for planning and review meetings.</p><p>People don’t realize how much work is multiplied by the use of email. You send an email to one person and that person is not only distracted by the notification but they have to read the email, perhaps scan down the chain of previous mails to get the context, then probably categorize or archive it. If the content wasn’t relevant to them, they’ve just wasted time and been distracted for nothing. If it was, then they may need to search for the mail to pull out that content later. Sure, outlook has some tools to help with all that, but now imagine you’ve sent the email to 10 people. The work time taken to process that email has now increased tenfold. This is in contrast to comments on a JIRA issue which are already archived and in context, or messages on a slack channel which can more easily be ignored or channeled.</p><p>A larger challenge I would say, and again it’s an obvious one, was that teams were distributed not just geographically but also across reporting lines. There were no cross-functional teams, and so every resource team needed a formal engagement, each with its own engagement process and funding model, which incurred more time and effort.</p><p><strong>Conclusion</strong>: When teams are distributed, more effort needs to be put into keeping them connected and synchronized. There are tools to help with this, and if all else fails we probably all have smart phones. Email sucks.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=94395f2707df" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>