<?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 Monroe on Medium]]></title>
        <description><![CDATA[Stories by Katie Monroe on Medium]]></description>
        <link>https://medium.com/@katie.monroe?source=rss-f493fae275c5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*f8ruE3TDtsP4EV1nzQQvbA.jpeg</url>
            <title>Stories by Katie Monroe on Medium</title>
            <link>https://medium.com/@katie.monroe?source=rss-f493fae275c5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 04:49:56 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@katie.monroe/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[lastpass at hks (dpi-662 blog post 3)]]></title>
            <link>https://medium.com/@katie.monroe/lastpass-at-hks-dpi-662-blog-post-3-f24d682ffbcf?source=rss-f493fae275c5------2</link>
            <guid isPermaLink="false">https://medium.com/p/f24d682ffbcf</guid>
            <dc:creator><![CDATA[Katie Monroe]]></dc:creator>
            <pubDate>Wed, 24 Oct 2018 00:33:10 GMT</pubDate>
            <atom:updated>2018-10-24T00:33:52.080Z</atom:updated>
            <content:encoded><![CDATA[<p>When I moved to Cambridge and started as a new student at the Harvard Kennedy School (HKS) last Fall, I remember being barraged by miscellaneous technology-related To Do List items. Connecting to school wifi! Downloading Zotero! Setting up email forwarding! Figuring out what two-factor authentication even means! Some tasks didn’t get done in this flurry of new-school activity. (It took me a full semester before I connected my laptop to the printers, for instance.) But signing up for LastPass, a password manager recommended by the school’s IT team, was one item I successfully checked off.</p><p>LastPass is offered to all Harvard affiliates as a free option while they are at Harvard. While I certainly interpreted this offer as a <em>suggestion</em> that I use it, using LastPass is not required for HKS students or staff. Given Harvard-specific protections already in place, as well as the implementation costs it would impose if done effectively, <strong>mandating the installation of LastPass for HKS students and staff would be an unwise move</strong>.</p><p>The concept of <strong>threat modeling </strong>is useful here. Before deciding how to allocate security resources, threat modeling is the process of fully exploring the nature of the specific applicable risks (and cost of defending against them). Different entities will have different “threat models” — for one city, it might make sense to worry about 9/11 style terrorist attacks, for instance, while it might not for another city.</p><p><a href="http://What do I want to protect? Who do I want to protect it from? How bad are the consequences if I fail? How likely is it that I will need to protect it? How much trouble am I willing to go through to try to prevent potential consequences?">Surveillance Self Defense</a> explains threat modeling as answering the following questions: What do I want to protect? Who do I want to protect it from? How bad are the consequences if I fail? How likely is it that I will need to protect it? How much trouble am I willing to go through to try to prevent potential consequences?</p><p>In this case, all of the login info for every site that students and staff at HKS use is a pretty big set of data to protect. However, Harvard Key’s two-factor authentication (see I did learn that!) is already in place to defend against attacks to our school email addresses and protect our access Harvard-specific sites. <strong>Compared to the status quo, mandating LastPass would provide greater additional marginal protection for our non-Harvard data than our Harvard logins. </strong>I imagine that an adversary who is targeting me because I am at Harvard would have less interest in my Pinterest account than my harvard.edu email address, so attacks to non-Harvard-related logins might be less likely. In addition, the consequences if Harvard fails to help me secure my Pinterest account are unlikely to be as significant for Harvard.</p><p>Currently, Harvard pays LastPass to provide free access to all Harvard affiliates. The price of this contract, plus some tech support hours for students who decide to sign up and need some pointers, is presumably the full LastPass-related cost on Harvard’s part. In a world where HKS mandates LastPass, the costs would be MUCH higher.</p><p>I am a student who chose to opt in to LastPass, and <em>even I didn’t fully do it right</em> — at some point over the past year I got logged out of the browser plugin, and faced some real confusion in trying to re-engage with the system for the purposes of this assignment. At one point, I thought all of my password data would have to be deleted from the site. If everyone at HKS were forced to sign up for LastPass, average enthusiasm/interest/attention to detail would be even <em>lower</em> than among the opt-ins, and many people would ineffectively use the product or need a lot of hand-holding when things went wrong. <strong>For all students and staff to be effectively using LastPass, a massive education campaign to generate buy-in would first be necessary</strong>, and a lot of tech support hours would need to be allocated to it. I am not convinced that the benefits of primarily safeguarding our personal login data would be worth this additional cost for HKS.</p><p>As Professor Waldo emphasized in class, technology alone does not and cannot guarantee security or privacy — law, culture, norms, etc. all play a role too. LastPass might make it <em>easier</em> to practice good password management, but students and staff would first need to be convinced that good password management is <em>important</em> to be motivated enough to use LastPass effectively. And a mandate wouldn’t make that happen overnight.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f24d682ffbcf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[massachusetts as a platform (dpi-662 blog post 1)]]></title>
            <link>https://medium.com/@katie.monroe/massachusetts-as-a-platform-dpi-662-blog-post-1-b51d30ba7a56?source=rss-f493fae275c5------2</link>
            <guid isPermaLink="false">https://medium.com/p/b51d30ba7a56</guid>
            <category><![CDATA[government]]></category>
            <dc:creator><![CDATA[Katie Monroe]]></dc:creator>
            <pubDate>Fri, 05 Oct 2018 20:59:56 GMT</pubDate>
            <atom:updated>2018-10-05T21:01:24.083Z</atom:updated>
            <content:encoded><![CDATA[<h3>massachusetts as a platform (dpi-662 blog post 2)</h3><p>[<em>note: this is an assignment for class and does not necessarily represent an actual recommendation to Governor Baker</em>]</p><p>The citizens of Massachusetts could greatly benefit from our Commonwealth moving toward a Government as a Platform (GaaP) approach to government, and I commend your foresight, Governor, in allocating funding to this effort. We have an opportunity here to set an example for other states to follow, and a corresponding responsibility to be thoughtful and strategic about implementation.</p><p><strong>What is GaaP?</strong></p><p>The word “platform” gets used in many ways. In this case, a platform is a software or service with a set of standards that allows outside actors to build on top of it in unexpected ways, creating value. A platform does not necessarily have to be high-tech: in a sense, our nation’s highway system was a platform built by the government. Allowing private citizens and commercial actors (as well as military and governmental actors) to use this system in whatever way they want — within reasonable regulatory limits — has undoubtedly created immense value for our country.</p><p>When we think about the Commonwealth of Massachusetts itself <em>as</em> a platform, the vision is:</p><ul><li>shared, underlying systems (databases, software, etc) for our departments and programs to work on top of</li><li>a future where departments are only doing work that is <em>specific</em> to their department’s mission, rather than managing duplicated vertically-integrated systems</li><li>increased efficiency and cost savings for current programs, and greater ease in launching new programs and getting them to scale</li></ul><p>We are far from this vision today. Where do we start?</p><p><strong>First Steps</strong></p><p>The ultimate goal of moving towards GaaP is to benefit the citizens of Massachusetts. Paradoxically, the best way to get there may be to start with an internal-facing, rather than citizen-facing, project.</p><p>In many ways, GaaP requires centralizing control of some systems and information away from individual departments, and is therefore likely to face pushback. GaaP’s success also rests on collaboration across departments, which can also be difficult. Ultimately, a move towards GaaP will benefit departments, as it will free them up to spend more time on their mission-critical tasks. In order to get there, we should begin with a project that creates value internally and builds buy-in for future GaaP projects.</p><p>In addition to choosing a project that will create immediate value for internal stakeholders, initial GaaP projects should meet the following criteria:</p><ul><li>not deal with particularly sensitive or risky information</li><li>have the potential to deliver significant cost savings</li><li>require collaboration between a relatively small number of entities</li></ul><p>Further analysis is needed to select a project that best balances all of these criteria. For example, if state government buildings across downtown Boston currently managed room reservations for meetings on different platforms, one potential example might be creating a shared system for booking rooms across government buildings.* Information about most meetings is not particularly sensitive (and some of it could even be made more public/open), centralizing could save significant money if vendors are being paid for separate room reservation systems, and if whole buildings rather than individual departments were currently on the different systems, it would only require coordination between a handful of actors.</p><p><strong>Governance</strong></p><p>In the long term future, a GaaP model raises many questions. One of the biggest ones has to do with power: with the underlying building blocks of government increasingly centralized, the governance and control of those building blocks is a very serious question.</p><p>It takes initiative from the Executive Branch to get the ball rolling on GaaP, and I commend your efforts here. As we move forward, new laws and regulations from our State House as well as important legal decisions from our courts will certainly inform the development of GaaP in Massachusetts as well. I cannot predict every new public conversation, task force, and piece of necessary legislation that will arise as we move toward broader GaaP implementation. It would be foolish to try to plan it all out in advance. But we won’t get there unless we take the first step.</p><p>I look forward to working with you to create a more efficient, productive, and agile Commonwealth for the citizens of Massachusetts, through Government as a Platform.</p><p>(*this is a made-up example.)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b51d30ba7a56" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[waterfall outreach and…agile engagement? (dpi-662 blog post 1)]]></title>
            <link>https://medium.com/@katie.monroe/waterfall-outreach-and-agile-engagement-dpi-662-blog-post-1-616f4ff9331d?source=rss-f493fae275c5------2</link>
            <guid isPermaLink="false">https://medium.com/p/616f4ff9331d</guid>
            <dc:creator><![CDATA[Katie Monroe]]></dc:creator>
            <pubDate>Sun, 23 Sep 2018 18:17:29 GMT</pubDate>
            <atom:updated>2018-09-23T18:17:42.936Z</atom:updated>
            <content:encoded><![CDATA[<p>In Spring 2015, I was part of the team that launched Philadelphia’s first bike sharing system, Indego. I was on staff at a bicycle advocacy and education organization, partnering with the City of Philadelphia, the bike share operator, national partners, and peer cities as part of a grant-funded effort to make bike share more equitable and inclusive, in Philly and beyond. The years I worked on this “Better Bike Share Partnership” effort (2014–2016) were among the most rewarding and challenging of my life, on both a personal and professional level. Years later, as a public policy grad student, I am still processing my failures and successes from this period.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*IhsJwS9HuKAXYwxU13myAA.jpeg" /><figcaption>joy + exhaustion captured in an early morning selfie on bike share launch day (philadelphia, april 2015)</figcaption></figure><p>My BBSP work had a lot of facets, but a huge part of it was spearheading Indego’s early community engagement and education efforts in neighborhoods throughout Philadelphia. This work began months before the bike share program even launched. My team reached out to neighborhood leaders and organizations in the neighborhoods where Indego would be launching to explain what was coming, gather input about exact station locations, and lay the groundwork for future partnerships. Once there were stations and bikes on the ground, much of the work took the form of an exhilarating (and relentless) event schedule: urban riding classes, tabling at neighborhood resource fairs, bike rides with community organizations — sometimes all of the above in a single Saturday.</p><p>Before I get to agile vs. waterfall (bear with me, DPI-662 reader, this is important) — many nonprofit and government folks, myself included, draw an important theoretical distinction between community <em>outreach</em> and community <em>engagement, </em>and strive to do the latter rather than the former as much as we can. Some <a href="https://static1.squarespace.com/static/54317469e4b056843fc6796c/t/553018e1e4b0389cde710c80/1429215457495/BTF-AssessYourWork.pdf">great work</a> by Partners in Building the Field of Community Engagement explains the basic differences:</p><p><strong>Outreach</strong> is transactional and short-term, with a unidirectional flow of information and a specific goal in mind (often buy-in for something already planned). Staff/institutions define both problems and solutions, and they keep the power.</p><p><strong>Engagement </strong>involves long-term relationship-building, a two-way flow of information and ideas, continual self-reflection and pivoting from original goals when appropriate. Community members are central to defining both problems and solutions, and they share/gain power through the process.</p><p>As I was reading about <a href="http://www.agilenutshell.com/agile_vs_waterfall"><strong>waterfall/planner</strong> vs. <strong>agile/learner</strong></a> modes of working, I started thinking about how these approaches might (or might not) map onto community outreach vs. engagement, and how these interrelated concepts could help explain some of the challenges my team faced as we managed the work of connecting Philadelphia communities with Indego.</p><p>Both waterfall and outreach mode are fairly straightforward: you plan what you’re going to do and you do it, and later you find out if it actually advanced your goals (oops). Early on in our BBSP work, we used a waterfall/outreach model. We made lists of neighborhood organizations to contact and set up meetings with them, created pretty calendars with schedules of events we wanted to hold in each neighborhood, and set targets for how many people we hoped to “reach” with our messaging and programming. We found partners willing to work with us on the types of events we had planned, and started finalizing our calendar.</p><p>This approach was effective at assuring our funders that progress was being made on the project, but when we actually started holding events, attendance at some of them was low. We had clearly not tested all of our assumptions about what types of events would resonate with people, and were relying in our planning on prior knowledge about bicycle programming which had involved both different types of bikes (non-bike-share) and communities (along race, class, neighborhood, age and gender lines).</p><p>Luckily, I think our team realized what wasn’t working pretty quickly, and we were able to shift to a more agile and responsive approach to our work, one that more quickly incorporated what we we were learning from Philadelphians. We asked questions at every event and listened to the answers, changing course accordingly. We learned, for example, that holding stand-alone events focused specifically on bike share was not the right strategy — partnering with organizations and taking part in/supporting <em>their </em>events worked better, so we started doing that. We also learned that there was a huge demand for Learn-to-Ride classes for adults, something we didn’t fully understand for from the start, so we added these to our calendar. These learnings were, fortunately, relatively easy to incorporate into our work. If we had been planning events that were harder to change (e.g. had already expended tons of resources on the logistical considerations and had to follow through), we might have had more problems.</p><p>In some ways, an “agile” approach and the “community engagement” model have parallels: both demand two-way information flow, a humbleness about how much you don’t know, and a willingness to change course as you learn. However, I think that true community engagement goes much further than speeding up iteration cycles and putting prototypes in front of end users more quickly and frequently to test assumptions and make sure you’re creating real value. <strong>At its best, deep community engagement breaks down the lines between designer and user, allowing both to share power and responsibility for co-creating products and programs in the long term.</strong></p><p>We did not always achieve this. Sometimes our work was merely “outreach” (and in certain important ways, it could never be more — after all, the bike share program was happening, one way or another). But other times, we got closer — for instance, in our Indego Ambassador program, where we hired community leaders to organize their own Indego community events, and provided them with logistical and financial support to do so. We built authentic, personal relationships with this inspiring group of people, some of whom are still working and partnering with Indego long after their official Ambassador term has expired, continuing to shape the future of bike share in Philadelphia even after many of the original staff have moved on.</p><p>I understand where an agile approach has value over waterfall, and will bring this lesson into future work. I am thinking in particular about better ways to communicate the value of this approach to foundations/funders, some (not all) of whom still prefer to see a detailed plan rather than a plan to learn. But I am also cognizant of how, in the context of community outreach/engagement, even a very successful agile approach might not achieve all that I hope to in my future work.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=616f4ff9331d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[philadelphia, 1/26/2017]]></title>
            <link>https://medium.com/@katie.monroe/philadelphia-1-26-2017-34dad85537c?source=rss-f493fae275c5------2</link>
            <guid isPermaLink="false">https://medium.com/p/34dad85537c</guid>
            <category><![CDATA[blacklivesmatter]]></category>
            <category><![CDATA[politics]]></category>
            <dc:creator><![CDATA[Katie Monroe]]></dc:creator>
            <pubDate>Thu, 26 Jan 2017 23:35:41 GMT</pubDate>
            <atom:updated>2017-01-27T00:12:48.761Z</atom:updated>
            <content:encoded><![CDATA[<p>You know how you can change your mood a little bit just by changing your face? How smiling makes you happier, not just the other way around?</p><p>I wonder if it works the same way when men chant “her body, her choice,” white people chant “black lives matter,” native English speakers learn the words to the chant happening in Spanish from their neighbor in the crowd of thousands of people marching around Philadelphia’s City Hall.</p><p>For the ones who are saying these things for the first time, the words strange and new to their tongues, encouraged by the moment we’re in, the crowd they’re in — does it make them believe it more to hear themselves say it out loud? Does it change the way they stick up for each other, what they contact their elected officials about, how they listen to and learn from and respect their fellow humans? Does it shift how they see the boundaries of their communities?</p><p>Make it so. Let those little shifts happen in you. Believe the things you chanted. Now believe them more. Now live those beliefs. I want to believe that the beautiful diversity of issues represented in the signs and chants at today’s march in Philly signals a burgeoning new coalition, a new recognition of the interrelatedness of all of our struggles, a new set of possibilities opening up.</p><p>I didn’t join the march today because I thought Donald Trump and Paul Ryan and all the rest were going to peek out of the windows of the Loews Hotel, hear our chants, and change their minds. I marched to change myself. I marched to make myself better.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=34dad85537c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[thoughts on a sabbatical]]></title>
            <link>https://medium.com/@katie.monroe/thoughts-on-a-sabbatical-1b00209d9c74?source=rss-f493fae275c5------2</link>
            <guid isPermaLink="false">https://medium.com/p/1b00209d9c74</guid>
            <category><![CDATA[travel]]></category>
            <category><![CDATA[hiking]]></category>
            <dc:creator><![CDATA[Katie Monroe]]></dc:creator>
            <pubDate>Mon, 29 Aug 2016 22:06:07 GMT</pubDate>
            <atom:updated>2016-08-29T22:06:07.207Z</atom:updated>
            <content:encoded><![CDATA[<p>For the past six weeks, I’ve been traveling. I took a luxurious, adventurous sabbatical for myself after four years of hard work in the Philadelphia nonprofit world. Packed up up my hiking boots, a tiny wardrobe, my wanderlust and a big pinch o’ privilege (I am well aware this type of trip isn’t possible for many folks) and set off to visit friends, visit colleagues, visit places I’ve always wanted to see.</p><p>The itinerary, in a nutshell: A day in NYC with my besties. Montreal with my boo. An idyllic lake in Ontario with my Philly lady crew for a weekend. Detroit to visit a bike share colleague and explore a city I’ve always been curious about. Visiting family in Michigan. Chicago for a few days. Over 45 miles of hiking in the course of a single week in Montana with my BFF and another childhood friend. Another week of hiking and biking with my parents and sister in the Pacific Northwest. Seattle adventures with college friends. Portland, at long last (people always assume I’ve been there before, bike lady that I am…I can finally say I’ve seen it!). Some time in San Francisco with my sister, a Phoenix visit with another college bud, and then back to Philly this week!</p><p>I have been joking that “the jury’s still out on whether this was a good idea — ask me when I’m employed again back in Philly,” but deep down I know I made the right decision this summer. I loved my work in Philadelphia, but by Spring 2016 I was getting worn down, burnt out, and honestly not as good at it as I had been. These past six weeks traipsing around the country, I have pretty consistently felt at peace, like I was exactly where I was supposed to be. As I bounced between epic national parks and fascinating cities, family and friends and strangers, I felt myself getting stronger. Hundreds of miles of hiking and biking and swimming strengthened my physical body, but mentally and emotionally I feel stronger than ever as well. Folks who know me know that I am a relentless extrovert — a constantly rotating cast of old and new friends to chat with in what kind of felt like one big ongoing conversation… is basically my dream! Only once or twice did I find the limits of my extroversion — everyone needs some me-time once in a while — but even noticing those limits felt like an important moment in my own journey of knowing myself.</p><p>I’ve tried to journal as I go along, and been only moderately successful at it. Instagram helps me remember, too. Some highlights I definitely don’t want to forget:</p><ul><li>Learning to enjoy lake swimming, sushi, and cats (don’t hate me for not being a fan of any of these before this summer! I am now!)</li><li>An all-female production of Julius Caesar at the base of Mont Royal Park, and great conversations with my fellow Shakespeare-loving boyfriend afterwards</li><li>Riding bikes on Belle Isle with a stranger I met in a coffee shop in Detroit</li><li>Getting let into the Art Institute of Chicago for FREE by my awesome art history friend Kat!</li><li>The Chicago architecture boat tour with a dear friend, during the *one hour* when it was pouring that day — still makes me giggle to think about us all peering up at the skyscrapers as raindrops fell in our eyeballs</li><li>Singing all the Girl Scout songs we knew to ward off Grizzly bears as my best friend and I hiked down a mountain in Glacier National Park. Also, watching the sun set from a kayak in the middle of a lake in Glacier (and feeling really safe from Grizzly bears there — yay, lakes)</li><li>Drinking champagne and talking about our careers with two dear childhood friends by a waterfall called Champagne Falls in Montana</li><li>Waking up in the middle of the night to watch the Perseid meteor shower with my family on the San Juan Islands — and then watching a family of otters playing the following morning!</li><li>Meeting the guy who took the most famous photos of Mt St Helens erupting, right after hiking around that strange post-apocalypic landscape (now blanketed in wildflowers)</li><li>Cheering on an old VW van named Bertha that got a little tired out on our way to a Seattle-area hike (but ended up making it to the trailhead!)</li><li>Figuring out Portland’s fancy new bike share program with Anna</li><li>Walking around Lake Merritt in Oakland with my sister and watching pelicans feeding up-close and personal</li><li>Frank Lloyd Wright and Sedona landscapes and much-needed catching-up with my friend Will</li><li>And so much more ❤</li></ul><p>And now it’s coming to a close, and I can’t wait to see Alex and my friends and the Philly skyline and my own bed and my own kitchen and my own bicycle! I feel ready to take the next steps of my career, whatever they may look like. I feel inspired to keep living my “normal” Philly life with some of the same zest for adventure I have embraced on this trip — there is so much I don’t yet know about my own city. And I feel incredibly grateful for the people who have hosted me and showed me the places they love, to the strangers who’ve made my adventure more interesting, to the huge beautiful country I live in, to my family for all they give me, and to myself for having the guts to buy some plane tickets and go for it. Thanks, all. Thanks, world. I’m ready to come home.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1b00209d9c74" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>