<?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 Katie Belanger on Medium]]></title>
        <description><![CDATA[Stories by Katie Belanger on Medium]]></description>
        <link>https://medium.com/@katiebelanger?source=rss-d767a74a8fd5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*kVGsoWTTvlXWfj0HcFO_Ig.jpeg</url>
            <title>Stories by Katie Belanger on Medium</title>
            <link>https://medium.com/@katiebelanger?source=rss-d767a74a8fd5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 09:44:46 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@katiebelanger/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[3 Steps to Ensure Teamwork Makes the Dream Work]]></title>
            <link>https://medium.com/@katiebelanger/3-steps-to-ensure-teamwork-makes-the-dream-work-f2f1de978fd1?source=rss-d767a74a8fd5------2</link>
            <guid isPermaLink="false">https://medium.com/p/f2f1de978fd1</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[nonprofit]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Katie Belanger]]></dc:creator>
            <pubDate>Fri, 04 Nov 2016 03:15:21 GMT</pubDate>
            <atom:updated>2016-11-04T03:15:21.591Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*uql8t0O3vxxsCGGUP8Qt2g.gif" /></figure><p>The strength of your team is the most powerful indicator of whether your organization will achieve its mission.</p><p>I’ve worked with teams of varying sizes across different sectors, and I’ve learned that high functioning and successful teams are collaborative, innovative, and results driven.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*vPHmNfyGJQig2Jd9hlOvQg.gif" /><figcaption>#SquadGoals</figcaption></figure><p>Technology has given us better tools to support high function teams. As the modern workplace continues to evolve and more of us are working in virtual offices or from the road, technology is also becoming the glue that holds our teams and organizations together.</p><h3>The Dark Side of Technology</h3><p>Though technology can solve problems, I’ve also found that many of our teams are struggling to keep up with technology. Emails, texts, tweets, Facebook posts, and myriad new applications promising to solve pain points can overwhelm us. Sometimes we spend more time triaging technology than getting our work done.</p><p>Besides managing incoming communications, poor technology integration can derail an entire team. If you’ve ever found yourself in a meeting where your coworkers talk more about the challenges your technology system creates than about advancing your mission, you know what I’m talking about.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*0gPQhZVMmb95oE_eDmaVfg.gif" /><figcaption>It doesn’t have to end like this.</figcaption></figure><p>It is critical that we figure out how to tame our technology and leverage it to better support our teams, and ultimately, advance our missions.</p><h3>But Before You Rush to Sign Up for That Cool New App…</h3><p>Don’t just pick a tool you <em>think</em> will help your team, announce that you’re going to use it, and expect everything to go swimmingly.</p><p>This. Will. Not. Work.</p><p>Trust me. I’ve done it.</p><p>Early on in my tenure as an Executive Director, I decided it would be helpful to have an organization-wide tool to help us keep track of and coordinate our work. I launched a search for the perfect app, selected one, and brought it back to the team. Folks were generally game to try out something new that could bring greater efficiency to our work.</p><p>It didn’t take long before we had entire meetings just about the project management tool. We discussed ad nauseam ways to triage inconsistent usage practices. I had one-on-one meetings with staff who didn’t keep their work up-to-date in the software at all. The tool didn’t add to the organization’s impact or our team’s success and, it was a great relief when we got rid of it, even though we were back to square one, a little worse for wear.</p><h3>Strategically Integrate Technology</h3><p>Technology tools really can be helpful. Since that failed experiment, I’ve helped integrate technology solutions to support many teams, including in traditional on-site office environments and for national and international businesses and nonprofits ranging in size from a small group of volunteer board members to staff teams of 100+.</p><p>I’ve created a three step process to strategically integrate technology in a way that will help your team and prevent the tools you use from eclipsing the work. As illustrated by the chart below, the steps include: understanding your team <strong>culture</strong>, focusing on specific team <strong>needs</strong>, and implementing and adjusting tool usage <strong>intentionally</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uclTZQhbeg9RgX9P9EgF4A.png" /></figure><h3>Step One: Understand your team’s culture, both current and aspirational.</h3><p>When I start working with a nonprofit, for-profit, campaign, or group of training participants, we first dig into the team’s culture. We do this by exploring the current and desired team culture and acknowledging challenges to the team’s ability to work together.</p><p>You and your team need to clarify how you want to work together, what you need to flourish, and what is difficult for your team to do. Through this honest assessment, you create the foundation for your overall team dynamics. It is this understanding that informs the second and third steps of this process.</p><h3>Step Two: Identify and focus on specific team needs.</h3><p>Now that you understand your team’s current and desired culture, you can determine what your team needs to succeed.</p><p>But we’re still not quite ready to dig into specific tools yet.</p><p>We start this phase by reviewing your strategic plan or strategic priorities. Executing and monitoring progress on your plan dictates what, how, and when your team needs to communicate and frames your internal communications systems. The level of cross-organizational collaboration laid out in your plan and team culture also impacts your team’s needs.</p><p>When you have a handle on your communication and collaboration needs you can finally get into selecting and implementing specific tools.</p><h3>Step Three: Implement and adjust technology solutions intentionally.</h3><p>Picking a tool and expecting a smooth and immediate adoption is unrealistic. Set your team up for success by identifying the small group tasked with choosing your technology solution. Including multiple people from the team who represent a variety of roles, technological savvy, departments, skills, etc. will ensure broad buy-in for the tool and increase adoption.</p><p>Once the tool is selected, carve out ample training time, both as a team to develop group usage agreements (e.g. how will you use it, are people expected to download the mobile app, how are notifications customized, etc.) and for individuals to get one-on-one coaching. Many tools will provide onboarding for teams at no cost, or provide online tutorials and webinars that the entire team can participate in or one person can use to develop a team-specific training.</p><p>It is critical that the work to implement a new technology tool does not end with the training. As you integrate the tool into the work, you may need to adjust usage expectations to meet a new reality or adopt application updates. I’ve also found it to be helpful to have at least 1–2 team members tasked with engaging with the tool on a regular basis to lead by example with the regular team. These team members’ vigilance will help prevent reversion to past practices.</p><p>The tool may also change the team culture or surface new needs. These three steps are an ongoing cycle of how team communication and tool usage evolve with your team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*j6HA3-xPQKEua_nxV8Pw4Q.gif" /><figcaption>Rinse and repeat.</figcaption></figure><p>Have you and your team experienced challenges with your internal technology systems? If so, post away in the comments — I’d love to hear your story!</p><p><em>Originally published at </em><a href="http://www.katiebelanger.com/blog/3-steps-to-ensure-teamwork-makes-the-dream-work"><em>katiebelanger.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f2f1de978fd1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dirty Words: On Becoming a Process Queen]]></title>
            <link>https://medium.com/@katiebelanger/dirty-words-on-becoming-a-process-queen-1d0f8fb0a1b0?source=rss-d767a74a8fd5------2</link>
            <guid isPermaLink="false">https://medium.com/p/1d0f8fb0a1b0</guid>
            <category><![CDATA[process]]></category>
            <category><![CDATA[team]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[nonprofit]]></category>
            <category><![CDATA[organizational-behavior]]></category>
            <dc:creator><![CDATA[Katie Belanger]]></dc:creator>
            <pubDate>Mon, 31 Oct 2016 00:22:39 GMT</pubDate>
            <atom:updated>2016-11-01T02:20:30.751Z</atom:updated>
            <content:encoded><![CDATA[<p>The year was 1986 and I was following a blue line down a long hospital corridor. The line, approximately four inches wide painted on the linoleum floor, stretched out as far as my eyes could see. It felt like miles to my five-year-old self. But I carried on. I had a job to do: navigate my mom and my grandma to whichever department the blue line would take us.</p><p>I used to have all the colors of the lines and their meanings memorized. Blue, green, red, orange, brown. One was for radiology, one for oncology, one for the laboratory, and so on. I remember my pride at being able to recall each one of them. Mom always said she couldn’t remember and thanked me for helping. Whether she really forgot or not, allowing me to take charge turned our countless trips to the hospital with my grandparents into an adventure.</p><p>For Grandma Alice, it was West Allis Memorial. For Grandpa John, it was the VA. For me, it was my pediatrician’s office when we had insurance; the urgent care clinic when we didn’t.</p><p>I observed everything. The systematic flow of patients from check-in to the waiting room to their appointments. The methodical transfer of paperwork between doctors and medical staff. The movement of bodies through different departments, to specialists, and back again. I made mental notes about the efficiencies and the inefficiencies I witnessed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*93yfe0UMM1kgInv7MjX5aw.gif" /><figcaption>Even as a child, I was always prepared…</figcaption></figure><p>Following that blue line helped it all make sense to me, solidified the rhythm of it all. Regardless of the reason for being at the hospital or the severity of the diagnosis, the blue line was always there. And if I followed it, I would always reach the same destination.</p><p>And thus began my love of process.</p><p>Process brings clarity, consistency, transparency, and safety to a tumultuous world. Process is the set of agreements we make with other people about how we are going to work together, what we can expect from each other, and how we hold each other accountable. Process is all around us — in our families, our friendships, our workplaces, our governments, our world. It is the foundation upon which everything is built.</p><p>Developing a solid process before launching directly into the work creates an opportunity to identify what you need to successfully accomplish your goals, anticipate and prepare for potential problems, ensure you’re including the right people and perspectives in your work, build buy-in from your team, boss(es), members, etc., and increase your overall efficiency in execution. And when things don’t go the way you thought (because life), you have a process to either assess potential new paths forward or cathartically throw out the window and start over.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*qJf2LqaEoxnnAc-ZL6tX0A.gif" /><figcaption>Process is better with magic and a dancing wizard.</figcaption></figure><p>A process can be as simple or complex as you or the task at hand requires. For example, the process I used to draft this blog post involved several writing and revision sessions, gif selection (super important), review by a friend and colleague for an outside perspective (thanks, David!), staring at the publish button for an awkwardly long period of time, and then hitting said publish button. That is a vastly uncomplicated process compared to the one I use to develop a new training curriculum, which involves many more individuals, intensive goal and metric setting, trainer and participant recruitment and onboarding, and…well, I think you get the picture.</p><p>Too often, “process” is used as a pejorative. We “process people” have been described as obstructionist time wasters who don’t value getting the work done. Process is also a gendered concept in our society. Women are often portrayed as process oriented and also less effective leaders while men are portrayed as decisive leaders who eschew process and deliver tangible results. This dichotomy has never been more tangible to me than in our current presidential election.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/467/1*J3piYMNgqSUnBDgdvYFnoQ.gif" /><figcaption>You know Hillz is a process queen.</figcaption></figure><p>The difference between process and anti-process people isn’t actually about the process — it’s a difference in leadership style and values. Leaders who integrate multiple people and perspectives in their work, who strive to create a shared understanding of goals and expectations, and/or who appreciate timelines and gaming out potential scenarios gravitate towards process.</p><p>It is true that process takes time. But I contend that the additional time spent on the front end to design a successful, thoughtful, and comprehensive process, will save time and energy in the end. And the team of people working together will have a more positive, productive, and engaging experience.</p><p>Sometimes even when people put the time in to develop a solid process, they still get stuck. They go round and round about different process options, unable to agree on actionable steps, timelines, or assignments. Even if they can agree on those elements, they may get stuck trying to develop contingency plans for every single possible scenario. Either way, the team has reached process paralysis.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*TGTHjEsnq7UAT1CExKUVag.gif" /><figcaption>Process isn’t always perfect and sometimes you end up with a shirt full of chocolates.</figcaption></figure><p>I am to process what a canary is to miners: I love process so much that if even I think things aren’t going well, get out. If I say you’ve gone too far on process, warning bells should sound and a search team should be sent out to ensure you safe passage home.</p><p>When people get stuck on process, it’s not usually the process that’s the problem. The challenge is more likely a lack of alignment on goals and outcomes. In other words, the person or group doesn’t agree on what they are trying to do, why they are trying to do it, or what the results of their work will be (or some combination of the three). Without answering those questions, it is nearly impossible to develop a successful process that everyone can agree on and execute.</p><p>So the next time someone suggests you spend some time on your process, thank the process person for saving you time down the road and then make sure you agree on your goals and outcomes before you dive in to create your own version of that blue line that will guide you and your team to your desired destination.</p><p>And if you are in need of a process queen, I know just <a href="http://www.katiebelanger.com/contact">the person to talk to</a>.</p><p><em>Originally published at </em><a href="http://www.katiebelanger.com/blog/becoming_a_process_queen"><em>www.katiebelanger.com</em></a><em>. “Dirty Words” is a series that explores organizational development, leadership, and productivity concepts that get a bad rap, but have the power to transform you, your work, and your organization.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1d0f8fb0a1b0" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>