<?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 Erin C Cummins on Medium]]></title>
        <description><![CDATA[Stories by Erin C Cummins on Medium]]></description>
        <link>https://medium.com/@erinccummins?source=rss-7a4eda6c9082------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*oZAIVzkEJ4ONmL9vGNevkg.png</url>
            <title>Stories by Erin C Cummins on Medium</title>
            <link>https://medium.com/@erinccummins?source=rss-7a4eda6c9082------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 17:20:10 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@erinccummins/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[my summer of croissants]]></title>
            <link>https://medium.com/@erinccummins/my-summer-of-croissants-abd79a343e2d?source=rss-7a4eda6c9082------2</link>
            <guid isPermaLink="false">https://medium.com/p/abd79a343e2d</guid>
            <category><![CDATA[baking]]></category>
            <category><![CDATA[summer]]></category>
            <category><![CDATA[croissant]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Erin C Cummins]]></dc:creator>
            <pubDate>Fri, 19 Aug 2022 15:35:15 GMT</pubDate>
            <atom:updated>2022-08-19T15:35:15.650Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="baked croissants on two baking sheets" src="https://cdn-images-1.medium.com/max/1024/1*yzbaq-Dflaz4z0_dSY7JeQ.jpeg" /></figure><p>In April of this year I decided to give myself the summer off because I was feeling stressed out, wasn’t sure if my job in product leadership was the right fit, and was distracted by the personal work I needed to do to figure out my marriage. Startup life can take a toll. My husband and I were at an impasse. I wasn’t happy, but I didn’t know what to do about it. Lots of ambivalence, lots of guilt.</p><p>I figured I needed a break. Perhaps with some space all around, I’d get some clarity. I gave my boss six weeks’ notice to help with a small portion of my guilt, and planned to wrap up my job by the end of May.</p><p>As someone whose job it was to make sure everyone was working on the most important thing at all times, the idea of a free summer off felt a little scary. I do best with some structure, so I set out to organize myself a little summer camp of sorts. I figured this would keep me from watching movies every day, getting depressed and having nothing productive to show for myself, which was for sure my biggest fear. Here’s what I envisioned.</p><figure><img alt="screenshot of a spreadsheet showing different planned activities across each day of the week" src="https://cdn-images-1.medium.com/max/1024/0*POar6CAujoYhFPJ1" /><figcaption>Yes, I actually made this at the start of my break.</figcaption></figure><p>I figured with an entire season off, I could write some short stories, master croissant baking, learn Italian, collect all the paperwork required to apply for Italian citizenship, and hopefully get back to my piano lessons and catch up on some of the classics I’d never read. Weekends I could take off.</p><p>Why croissants? I’m not sure why I’d always considered them to be my white whale of baking, but it probably has something to do with how much I like eating them. I remember fully falling in love with them after moving to the West Village from New Jersey to start grad school. Patisserie Claude on West 4th Street had the best croissants–plain, chocolate and almond. Sadly, Claude has retired and the place hasn’t been the same since. The almond croissants still have that creamy filling in them, though, not just the heavy marzipan and candied almonds that everyone else seems to pack them with.</p><p>And let’s be real, this isn’t like firing out some chocolate chip cookies. As early as I can remember, people have been telling me that croissants are hard to make or are too much work (and to make something easier instead). I knew that it would take more than one batch to get it right. Perhaps such a level of difficulty could substantiate three months without a real job.</p><h4><strong>Batch 1 : We knew this wasn’t going to be easy</strong></h4><p>My first batch suffered from a lack of understanding of just how delicate the dough is, and how easily the butter can melt across the several steps along the way. For my first shot, I used <a href="https://www.seriouseats.com/how-to-make-croissants-french-pastry-recipe">this detailed recipe from Serious Eats</a>. I had some challenges, and so I bet this recipe comes out better with some experience. (I have not yet tested it a second time.)</p><p>I pounded out this chilled block of butter into a square of parchment, and placed it on my rolled out dough, which I had made the day before. The dough gets folded around the butter, rolled, folded, chilled, rolled again, etc.</p><figure><img alt="dough rolled out with a flat block of butter on top of it" src="https://cdn-images-1.medium.com/max/1024/0*ZoGPMWdr4ekge3p8" /></figure><p>My favorite part: the book fold!</p><figure><img alt="laminated dough folded up into 4 layers" src="https://cdn-images-1.medium.com/max/1024/0*Q77KQBnSjdpW5JcC" /></figure><p>Dough can tear if it gets too warm or sticky! I didn’t use enough flour, or maybe didn’t keep the dough cold enough, so I had some trouble getting these guys off of the countertop without tearing them. If you look closely at these delicate triangles you can see some yellow butter peeking through along the bottom edge.</p><figure><img alt="rolled out dough sliced into 12 triangles" src="https://cdn-images-1.medium.com/max/1024/0*sdHJqo3cjY2U-2v-" /><figcaption>my first triangles</figcaption></figure><p>The thin butter layers will melt right out of those crescents if you try to proof (rise) them too warm! I learned this by putting a warm skillet of simmering water into the oven, but not realizing that I needed to wait for the oven to cool down before putting the rolled croissants in to proof.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*kq-9_ViAs9dtq1KC" /><figcaption>Seeing the butter leak was heartbreaking, but I persevered.</figcaption></figure><p>The final form was tasty but nowhere near as fluffy and flakey as I wanted.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*alWYwPy3fK6gZ17p" /><figcaption>Golden brown but quite flat</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rg6Nemam9oYmPBho" /><figcaption>Batch 1 crumb shot —lacking air</figcaption></figure><p>Luckily our dear friends Rob and Nichole were staying with us for John and Margaux’s wedding, and were ready to help eat these flat little experiments.</p><h4><strong>Batch 2: C<em>lose enough</em></strong></h4><p>After a couple weeks off to recover, I was ready to use what I’d learned and try again. Batch 2 was made using<strong> </strong><a href="https://cooking.nytimes.com/recipes/1022053-croissants">Claire Saffitz’s recipe for the New York Times</a>. You can also watch <a href="https://www.youtube.com/watch?v=vpwY3nmLLaA">her video here</a>.</p><p>This recipe worked out better for me because it was very specific about when to chill the dough in the refrigerator or freezer between folds. (Folds are the steps of rolling out and folding (“laminating”) the butter with the dough, to make the layers.) I had also learned from my mistakes last time and was much more careful about not letting the dough stick to the counter.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LtAo5S1MjqbowLZi" /><figcaption>Bigger triangles</figcaption></figure><p>It’s also worth noting that this recipe is larger (has larger amounts of ingredients), but it makes fewer croissants than the Serious Eats recipe, so it makes sense that they turned out much bigger and poofier looking.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wCVT2kOxvhxUV3Qe" /><figcaption>An elongated triangle, ready to roll</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uFzLBMgI5H4Mobc4tFwCtA.jpeg" /><figcaption>Batch 2 rolled up, already looking bigger and better</figcaption></figure><p>Once proofed, these guys were jiggly! And not melted!</p><figure><img alt="four raw croissants on a baking sheet" src="https://cdn-images-1.medium.com/max/1024/0*sXabpE2963wY1txN" /><figcaption>Batch 2 awaiting their egg wash</figcaption></figure><p>As you can see, they flattened out a little while baking. I think refrigerating as soon as you think they’re done proofing helps keep their shape as tall as possible when you put them into the oven. The challenge there, of course, is clearing out room for two baking sheets in your fridge. Next time I’ll let them take turns in the fridge before baking. (I think the refrigerated ones are shown in the front here, if I recall correctly.)</p><figure><img alt="eight golden brown croissants on two baking sheets" src="https://cdn-images-1.medium.com/max/1024/0*Qb0gHvUcsNUOJB5i" /><figcaption>Batch 2 — success!</figcaption></figure><p>I was quite happy with Batch 2, and immediately raced around Brooklyn, delivering them to my friends who were so kindly willing to eat them. (Thank you Hannah, Margaux, Tom and John. And of course Drew, my main eater.)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7gtpBbM3hYH-uHWM" /><figcaption>Batch 2 crumb shot — a little better!</figcaption></figure><h4><strong>Batch 3: C<em>innamon morning buns, my first baking riff!</em></strong></h4><p>Fresh off of Batch 2’s success, I was ready to try something new. I wanted to show off my dough lamination skills, and use another favorite treat as inspiration–cinnamon rolls.</p><p>So I rolled out my next batch of laminated dough as thin as I could without it tearing, and sprinkled a lot of cinnamon and sugar inside. Then I rolled them up and proofed overnight.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9-WMXXVHmdIDuYiK" /><figcaption>My beautiful, buttery, raw spiral slices</figcaption></figure><p>These were overall much easier to handle, and came out nice with little drama. While I did have to deal with the dough sticking to the counter while rolling it up, it helped that I didn’t have to cut out all those triangles and roll them up individually. The “snail” shape felt less temperamental.</p><figure><img alt="Nine freshly baked morning buns on a baking sheet" src="https://cdn-images-1.medium.com/max/1024/0*8H4Ili1RB8pOElYu" /><figcaption>Fresh out of the oven–they really puffed up!</figcaption></figure><p>They were pretty for sure, but a little boring. So I made a cinnamon glaze with powdered sugar, milk, cinnamon and a tiny pinch of cayenne.</p><figure><img alt="morning bun on a plate" src="https://cdn-images-1.medium.com/max/1024/0*N2uLOX6ZQANN4wlN" /><figcaption>Iced with a cinnamon-sugar glaze. These were really tasty.</figcaption></figure><p>With the successes of making relatively passable croissants, and then riffing on them, I’m ready to close this chapter of my life. Croissants are hard! I’m grateful to have had the time and support to check this achievement off of my list.</p><p>As for the classics, I did read <em>Jane Eyre</em>, thanks to my wonderful friend Julia!</p><p>And for my Italian Citizenship, I got pretty far, but Grandma’s names aren’t matching up, so her birth certificate might need corrections, which is no small task. I also have no idea if my requests made it to Italy, if they will be answered, and if so, whether they’ll make it back to Brooklyn. This is not an easy endeavor, but as they say, things that are worthwhile tend not to be.</p><figure><img alt="messy kitchen counter showing flour, a knife, bench scraper, measuring tape and rolling pin" src="https://cdn-images-1.medium.com/max/1024/0*qQHJflJkzxkwRdD3" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=abd79a343e2d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Live-Music-Shaped Hole In Our Pandemic Lives]]></title>
            <link>https://medium.com/@erinccummins/the-live-music-shaped-hole-in-our-pandemic-lives-7aae14cbdbe?source=rss-7a4eda6c9082------2</link>
            <guid isPermaLink="false">https://medium.com/p/7aae14cbdbe</guid>
            <category><![CDATA[live-music]]></category>
            <category><![CDATA[new-jersey]]></category>
            <category><![CDATA[concerts]]></category>
            <dc:creator><![CDATA[Erin C Cummins]]></dc:creator>
            <pubDate>Sun, 02 Aug 2020 17:45:14 GMT</pubDate>
            <atom:updated>2020-08-02T17:45:14.559Z</atom:updated>
            <content:encoded><![CDATA[<p>Waiting in front of Mayer’s Tavern for a late July beach vacation dinner, counting the number of patrons with their masks on, I heard a familiar guitar strum, the refrain “faaaaaaade into you.” The sound of a muffled bar band* covering an old favorite reminded me how much I missed live music. It didn’t matter that Mazzy Star, Radiohead and Neil Young weren’t there in Cape May. I got to hear a more-than-decent band play my favorites over an open-air dinner, and it was a glorious surprise.</p><figure><img alt="Mayer’s Tavern, Cape May, NJ" src="https://cdn-images-1.medium.com/max/1024/1*NMSmFzdelu9iHYLCld6umA.jpeg" /><figcaption>Mayer’s Tavern, Cape May, New Jersey</figcaption></figure><p>New York has been living without any live entertainment since March. Summerstage, canceled. Celebrate Brooklyn!, canceled. New albums are coming and going without tours.</p><p>Before the pandemic, concerts were one of the things that kept me going. Like little vacations (and we all know travel is out for a while), live shows were breaks I would look forward to between stressful workweeks. I have “concert friends” I haven’t seen in ages. I miss my favorite spot between the trees at the Prospect Park Bandshell, and the $8 canned rosé. These shows were 3-hour escapes, a 10 minute walk from home.</p><p>As Sarah Cracknell sings about being too young for live shows in Saint Etienne’s “Over the Border,” we all know what it’s like to wait, to yearn.</p><blockquote>A few weeks and I’d be free<br>A few weeks and music wouldn’t have to be so private, it would be there for me</blockquote><p>The snippets of live music we hear while gathering is still not allowed remind us of how important it is. You hear the energy in the protest chants, drums and songs at the Black Lives Matter marches, and can even feel soothed by the late night comedy show band members playing their usual hooks, remotely from home. We’re finding ways to keep live music around us, because it helps to keep us going through this time, just like when we were 17.</p><p>“Over the Border” ends with the hope that music would continue to permeate her life:</p><blockquote>It would be there for me, and when I was married, and when I had kids <br>Would Marc Bolan still be so important?<br>Over the border, I’m growing older, heaven only knows what’s on its way<br>Every single day, love is here to stay</blockquote><p>Special thanks to Perfume Genius, Fiona Apple, Taylor Swift, Lianne La Havas, Phoebe Bridgers, The Weeknd, Glass Animals, Jarvis Cocker, Angel Olsen, Father John Misty, Beyoncé, Bright Eyes(!), and everyone else who I don’t know yet for giving us both wonderful music to listen to now, and the hope for something to look forward to on the other side. I can’t wait to dance with you all.</p><p>*the band at Mayer’s was <a href="https://www.instagram.com/claviclesmusic/">Clavicles</a> and they were fantastic! Get the scallops.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7aae14cbdbe" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 Qualities You Need in an Agile Product Manager]]></title>
            <link>https://medium.com/@erinccummins/5-qualities-you-need-in-an-agile-product-manager-3bba981e4d18?source=rss-7a4eda6c9082------2</link>
            <guid isPermaLink="false">https://medium.com/p/3bba981e4d18</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[hiring-for-startup]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[founders]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Erin C Cummins]]></dc:creator>
            <pubDate>Wed, 27 Mar 2019 14:50:04 GMT</pubDate>
            <atom:updated>2019-03-27T14:50:04.885Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e7O7A5rM79ng6b8Dc3EbEg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/RLw-UC03Gwc?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Glenn Carstens-Peters</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Startup founders, who are often very happy to stay hands-on with their team’s software development, will eventually have to step out of those weeds to focus on bigger and better things. When managing the day-to-day development turns into a full time job, it’s time to add a new role: product manager.</p><p>Small teams, however, actually need <strong>a blended <em>project</em>-product manager</strong>, who will handle all of the Agile processes that determine the <strong><em>when</em></strong> as well as the <em>what</em> of what is being built.</p><p>When hiring a product manager for this role, it’s important to look for the skills and qualities of someone who will be able to keep a project <strong>on track and on time</strong>, in addition to running the product definition phase of new feature development. Here are some things to look for in someone who will be handling both of these jobs.</p><p><strong>Tip</strong>: Candidates with agency experience will likely excel here. Client services often require more clearly defined project expectations and stricter budget adherence than early startups do.</p><h3><strong>1. Experienced</strong></h3><p>Be clear that project management will be expected in this role, and look for someone who has has some experience either in project management or client services. They should have some understanding of or willingness to learn <strong>timeline and budget management </strong>so that they understand the seriousness of projects that don’t stay on schedule.</p><p><strong>Ask</strong> how they handled a past project that wasn’t going to be finished on time. Good answers will include a renegotiation for a leaner MVP that includes input from various stakeholders. You’ll want a PM who isn’t afraid to get your input when they need it.</p><h3><strong>2. Assertive</strong></h3><p>At a bare minimum, you need someone who is going to <strong>speak up when something might be going wrong</strong>, and ask questions when they’re not sure. Even better, a great PM will challenge your ideas, question your assumptions and make sure your software solutions match your business goals, rather than simply build what you ask for.</p><p><strong>Ask</strong> them about a time they asked for help.</p><h3><strong>3. Agile</strong></h3><p>Experience with the Agile methodology, even just for a year or so, will be very helpful here. This framework empowers product managers to implement the <strong>highest priority items first</strong>, resulting in a testable MVP sooner than the waterfall method would.</p><p><strong>Ask</strong> how they would prioritize a backlog of features and bugs. Look for answers that focus on <strong>user and revenue impact</strong> or ROI. Bonus points if they suggest how success will be measured.</p><h3><strong>4. Transparent</strong></h3><p>A manager who has set up project-based communication channels in the past will be more likely to <strong>earn their new team’s trust and be up and running more quickly</strong>. They should also be open to team input and feedback on their process.</p><p><strong>Ask</strong> them what their favorite project management tools are. Find out what processes they’ve implemented in the past that helped their teams and/or stakeholders stay abreast of project process.</p><h3><strong>5. Collaborative</strong></h3><p>This manager is going to need to work closely with you, designers, developers, QA, client services, sales and marketing, and possibly your boss and your clients, too. They need to be able to <strong>build</strong> <strong>strong, trustworthy relationships across your organization</strong> in order to successfully handle both the product and project management of your roadmap.</p><p><strong>Ask</strong> about the relationships they’ve built at other organizations. You can even ask about how they handled a challenging colleague to see if they are able to work with different personalities and <strong>stay focused on positive outcomes</strong>.</p><h3><strong>Need help?</strong></h3><p><a href="https://www.linkedin.com/in/erincummins/">Get in touch here</a>, and I’ll help you with your job description, interviews, and even help set up your Agile development process.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3bba981e4d18" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Protecting Your Team from Uncertainty]]></title>
            <link>https://medium.com/@erinccummins/protecting-your-team-from-uncertainty-24ad80ef8380?source=rss-7a4eda6c9082------2</link>
            <guid isPermaLink="false">https://medium.com/p/24ad80ef8380</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[founders]]></category>
            <dc:creator><![CDATA[Erin C Cummins]]></dc:creator>
            <pubDate>Wed, 20 Mar 2019 14:54:02 GMT</pubDate>
            <atom:updated>2019-03-20T14:54:02.323Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mCNBPIzmCSBUSdJznrVxtA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/4eqOc39NCRQ?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Ricardo Resende</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>All managers have a responsibility to shield our teams from the distraction and stress of outside influences. Product managers, specifically, work hard to create tightly prioritized sprints for high priority releases that can easily be pulled off course by a seemingly innocent conversation.</p><p>Protect your team from the uncertainty that can come from wayward requests, feedback and rumors from other teams, and <strong>keep them focused on their current priorities. </strong>Nothing should be left up to interpretation, and your team will appreciate you managing their workflow and cross-team communication.</p><h4><strong>1. Give Them Certainty</strong></h4><ul><li>Make sure there’s always <strong>clearly defined work</strong> lined up. If a team member gets word of a new feature idea and wants to know if they should be working on it, point them to the stories in their current sprint as their current priority.</li><li>Ensure new feature requirements are super clear and cover all use cases before scheduling them for your team.</li><li>Keep distractions about potential new initiatives to a minimum until both priority and requirements are firmed up. Don’t ask for their input until you’ve had a chance to <strong>think it through</strong>.</li></ul><h4><strong>2. Address Uncertainty</strong></h4><ul><li>Work closely with stakeholders to <strong>own the conversation about new features</strong> and make sure you understand the business need.</li><li>Be transparent with stakeholders about the roadmap and get feedback from higher-ups if you need help prioritizing. This will protect your team from questions about <strong>what they are working on and why</strong>.</li><li><strong>What to say</strong> if someone on your team asks about something new? “We’re still working out the details. I’ll schedule a meeting to get your input soon.”</li></ul><h4><strong>3. Control Communication</strong></h4><ul><li>Minimize feature requests from stakeholders / upper management made directly to designers and developers by making sure they know that the <strong>requests should come to you</strong>. <a href="https://medium.com/@erinccummins/4-quick-ways-to-make-time-for-product-management-d8f76661ea68">Anticipate their needs</a>.</li><li>Develop good relationships with your internal and external stakeholders so that they feel heard when they have new feature ideas and client/user feedback. <strong>Leverage their expertise</strong> whenever possible.</li><li>Develop good relationships with your team members so that they loop you in whenever they are passed requests directly. They should appreciate you <strong>taking the burden off of them</strong> to deal with the request.</li></ul><h4><strong>4. Head Off Wayward Requests</strong></h4><ul><li>Schedule regular, <strong>recurring meetings</strong> with stakeholders so that they know there will always be time for their input. Creating a time and place to be heard will help curb their urge to pass feature requests directly to your team members.</li><li>Step in if you hear a wayward request brewing. In-person or on Slack, politely say that <strong>you’re in charge of scheduling all requests and want to make sure you understand the need</strong>. Interrupting their conversation (and your own work) isn’t ideal, but it can be a necessary part of training your colleagues.</li></ul><p><strong>What else?</strong> I’d love to hear from other PMs about how you keep your teams focused at fast-moving startups and organizations with lots of distractions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=24ad80ef8380" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[4 Quick Ways to Make Time For Product Management]]></title>
            <link>https://medium.com/@erinccummins/4-quick-ways-to-make-time-for-product-management-d8f76661ea68?source=rss-7a4eda6c9082------2</link>
            <guid isPermaLink="false">https://medium.com/p/d8f76661ea68</guid>
            <category><![CDATA[product-manager]]></category>
            <category><![CDATA[founders]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Erin C Cummins]]></dc:creator>
            <pubDate>Wed, 13 Mar 2019 14:20:30 GMT</pubDate>
            <atom:updated>2019-03-13T14:21:13.827Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>4 Quick Ways to Make Time for Product Management</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7UuxflUiid1k12tRz_EA8Q.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/FfbVFLAVscw?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Malvestida Magazine</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>One of my greatest challenges as a product manager of a startup has always been making time to do the actual product management work. The day-to-day <em>project</em> management that falls on this role, quick feedback needed on delivered work and the never-ending need to address blockers were always more urgent than the longer term research needed to support new feature exploration, which is the core of the PM role. I believe <strong>this devalues product management</strong>, both as a concept and as a valued role in an organization.</p><p>So, how does a product manager make the time to be a good product manager? The key for me is to block out time to do the product work. Accomplish this by minimizing task switching, heading off interruptions, prioritizing your work and <a href="https://medium.com/@erinccummins/product-management-time-blocking-for-your-sanity-a1319d807a06">actually blocking off the time</a>.</p><h3><strong>1. Minimize Task Switching</strong></h3><p>Minimizing the number of times you switch tasks or topics will save you the minutes it takes for your brain to change gears. This will also save you some mental energy, allowing you to get more done in a day while (hopefully) feeling less exhausted at the end of it. I personally find that I’m most tempted to check Facebook/Twitter/Reddit when I’m in between tasks, so this will minimize those opportunities, too.</p><p>I do this by <strong>bundling work together, by project,</strong> and actually putting it on my calendar. Say you’re managing two projects, all of which will need some notes from QA reviewed, work checked, and some new stories written at some point in the day. Block out some time, say 30 minutes per project, where you’ll be able to hit all three of those tasks for that project at once. You may need to do this twice a day per active project in order to give quick feedback, and that’s okay. Having two dedicated chunks of time for a project is much more efficient and less disruptive than turning your attention every time a new story is delivered or a question comes up — <strong>that could be a dozen times in one day.</strong></p><p><strong>Tip</strong>: If there’s also some<strong> <em>product</em> work</strong> to be done that’s related to this project, try to schedule that work at the same time, or right after. It will keep your brain in a similar mental space, as it’s not much of a hurdle to start thinking about what should come next while you’re dealing with what’s going on now.</p><p><strong>Extra credit: </strong>Just completed a big block? Reward yourself with a walk for coffee or lunch, or even a quick breathing exercise. This will refresh your mind for your next task.</p><h3><strong>2. Anticipate Interactions</strong></h3><p>You can minimize interruptions by anticipating interactions from your team members. Take ownership of the active items in your purview and be proactive about communication, otherwise, you’ll be interrupted by these folks when they have tasks or feedback for you. This has two major benefits: <strong>you get to control when you talk about these things</strong>, and you look very much on top of your stuff.</p><ul><li><strong>Regular meetings</strong> — Weekly or monthly recurring meetings with stakeholder groups create a dedicated space for product feedback, client and customer learnings and plans for upcoming initiatives and events. <strong>Fewer surprise feedback sessions</strong> will pop up if colleagues know they have some dedicated time coming up soon.</li><li><strong>New projects</strong> — Get a stakeholder exploratory meeting on the calendar as soon as you hear about a new initiative that you’ll be managing. <strong>This <em>should</em> keep them from popping by your desk</strong> when they feel like talking to you about it.</li><li><strong>One-on-ones </strong>— Ask your boss for a weekly one-on-one where they can update you on new work coming up. If this is blocked off at a regular time, you’ll both be able to <strong>plan ahead</strong>.</li></ul><p>Being proactive about these interactions allows you to schedule them for a time that works for you. Knowing that they have regularly scheduled, dedicated time coming up with you will help keep coworkers’ DMs and emails at bay.</p><p><strong>Tip</strong>: Recurring meetings are a great way to minimize time spent scheduling new meetings when you need to talk, and can always be canceled when you don’t need them.</p><p><strong>Extra credit</strong>: Try to schedule meetings in succession if you can. This will help maximize the size of the uninterrupted “working time” blocks you’ll have left for product management.</p><h3><strong>3. Prioritize</strong></h3><p><strong>Don’t let Slack and your inbox dictate</strong> when you deal with a particular issue. Keep a prioritized to-do list to keep your day focused, and block off time to review your inbox and Slack.</p><p>I like to keep a running list of my day’s priorities, organized by both priority and project. During my inbox and Slack reviews, <strong>I don’t necessarily deal with new issues as I see them</strong>. Any items that will take more than two minutes to address get prioritized on my day’s to-do list along with everything else. (Items that <em>can</em> be done in two minutes are best handled then, since you’re already thinking about them.)</p><p><strong>Tip</strong>: I love Wunderlist for this. The simple interface makes it easy to add and prioritize your items, and the app makes a wonderful little “ding!” when you tick something off. I like to keep my three “must do” things for the day at the top, with my priorities for the week right below where they’re always visible.</p><h3><strong>4. Schedule Time with Yourself</strong></h3><p>Finally, get some blocks of time on your calendar, preferably <strong>30 minutes to an hour at a time, to dig into your product management work</strong>. Put on headphones or grab a room to avoid interruptions. You want to be able to read, explore, draw, write and think creatively, and your brain needs uninterrupted chunks of time in order to do that.</p><p>And as for what to prioritize once you’re in the product zone, that’s for another post.</p><p>Read <a href="https://medium.com/@erinccummins/product-management-time-blocking-for-your-sanity-a1319d807a06">more of my thoughts on time blocking here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d8f76661ea68" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Think You’re Ready To Hire? Try These 5 Process Improvements First]]></title>
            <link>https://medium.com/@erinccummins/think-youre-ready-to-hire-try-these-5-process-improvements-first-af37a2d95171?source=rss-7a4eda6c9082------2</link>
            <guid isPermaLink="false">https://medium.com/p/af37a2d95171</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[process-improvement]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[scaling]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Erin C Cummins]]></dc:creator>
            <pubDate>Tue, 05 Mar 2019 14:40:12 GMT</pubDate>
            <atom:updated>2019-03-05T14:40:12.364Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/804/1*a2RWhc_0P9vP7BklCWTQNg.png" /><figcaption>Image by Samuel Lee Miller</figcaption></figure><h4>Getting more out of the team you have, and making them happier, too</h4><p>You’d like to start shipping new features more quickly, and you’ve wondered if your team’s productivity could be boosted with some process improvements. You can always hire more people, but there might be a cheaper way to get a more done faster. Here are a few common process efficiency flags to watch for.</p><h3><strong>1. Priorities</strong></h3><p>Is the whole team laser-focused on MVP features, or have you noticed some people spending time on nice-to-haves before your most important items have been released?</p><h4><strong>The Fix</strong></h4><p>Make sure there is a clear product roadmap that is being followed by the PM or whoever is running development. You may need to clear up how important it is to have the core MVP version of your product complete by a certain date. <strong>Set some milestone deadlines</strong> to keep the plan on track.</p><h3><strong>2. Bottlenecks</strong></h3><p>Are there any team members that don’t have much work to do, or aren’t sure what they should be working on?</p><h4>The Fix</h4><p>Check with the PM, if you have one, and look upstream. Developers should always have clearly detailed user stories to work on from the Product Manager, including annotated design specs. Designers should always have a <strong>prioritized</strong> roadmap of product features to churn out. It’s the PM’s job to make sure this is all happening. There should be a clear, <strong>prioritized</strong> section of user stories (usually the “To Do” column) that are ready to be worked on from the top, down. (Note: any stories that aren’t actually ready should be moved back out. Allowing blocked stories to remain in the To Do column causes confusion.)</p><p>Already have a PM? Sit down with them to find out where workflow is lagging and what you can do to help. Make sure there is a crystal clear, <strong>prioritized product roadmap</strong> of features for the team to work on for the next few sprints. Make sure the PM has time to flesh out the feature requirements for the upcoming features.</p><p>Don’t have a PM? Consider hiring one, <a href="https://medium.com/@erinccummins/10-signs-your-team-is-ready-for-a-product-manager-4ccfe2beb9d3">especially if your organization is showing other signs of needing a one</a>. A dedicated PM will make sure work is correctly prioritized and properly documented with requirements ahead of every sprint.</p><p>Alternatively, you can put someone else in charge of making sure everyone always has (the right) work. Keep in mind this will affect that person’s usual deliverables.</p><h3><strong>3. Blockers</strong></h3><p>Are developers often blocked with questions about implementation during development? Blocking issues can waste a lot of developer time, especially if they get stuck waiting for an answer. Experienced product managers know how to avoid this by ensuring requirements are fully fleshed out before work begins.</p><h4>The Fixes</h4><ol><li><strong>Communication</strong> — Encourage team members to speak up when they are blocked. A transparent venue like a Slack project channel is a great place to make everyone aware of the blockage and encourage collaboration on the solution.</li><li><strong>Beef up your user stories</strong> — If user stories (tickets) aren’t properly detailed with requirements for <strong>all use cases</strong> and annotated designs, your developers are going to have a lot of questions. Your PM may need some coaching on what good user stories look like, and if your process has been rushed they may also need more time to prepare them. Without properly detailed stories, development is going to be slowed by implementation questions, functionality debates and brain power lost to context switching.</li><li><strong>Sprint/iteration planning &amp; feature kick-off meetings</strong> — Before new feature development starts, the user stories, requirements and designs (if applicable) should be reviewed by the project team. Developers should speak up with questions about use cases and functionality at this time, saving development time by avoiding blocking questions later.</li></ol><h3><strong>4. Emergency Pace</strong></h3><p>Is the team always rushing to complete work in emergency mode? Do they work late and weekends to keep pace or get something out for a special client? This is problematic, because it’s bad for morale and is probably costing you in bad code and ill-thought-out product decisions. <strong>These features will need to be reworked later</strong>, often as yet another last-minute fire drill to account for a missed assumption.</p><h4>The Fix</h4><p>Have a plan set ahead of time and work on limiting last minute requests. The PM, designer and engineers all need time to work out the best solutions to ensure efficiency, scalability and sanity. Listen to team input for creative solutions to the business opportunity or problem. Being transparent about the opportunity can help with team buy-in and offer more opportunities for creative problem solving.</p><h3><strong>5. Knowledge Gaps</strong></h3><p>Are junior software developers often stuck on difficult problems?</p><h4>The Fix</h4><p>Encourage developers to help each other with tough problems. Reasonable delivery timelines will help here— a senior engineer will be more likely to lend a hand if they aren’t stressed out about their down deadline. A good PM will always be on the lookout for opportunities for team members to help each other, as this will make the whole team more efficient.</p><h3>Measuring Velocity</h3><p>Want to know which changes are actually improving output? Make sure you have the story points feature of your tracking tool turned on, and that all user stories are assigned points. This is usually done during (bi)weekly iteration and sprint planning meetings. This is the data that you need to iterate on your process.</p><h3>Ready to grow the team?</h3><p>Process checks out? Here are some signs your organization is ready to hire.</p><h4>Developers/Engineers</h4><ul><li>You have well-defined product requirements and designs ready, waiting for developers to work on them.</li><li>You don’t have many blockers or lack or work issues from the Process issues above.</li><li>You have one or more junior developers falling behind schedule who could use help from a more experienced developer.</li></ul><h4>Designers</h4><ul><li>You have developers waiting for work due to new feature designs not being ready, and this does not appear to be a short term problem.</li><li>You don’t have enough UI/UX work for another full time designer, but may have some marketing materials they could work on while you ramp up.</li></ul><h4>Product Managers</h4><ul><li>You have some new features in mind with the designers or developers to work on them, but don’t have time to explain to the team what they should start building.</li><li>You have some opportunities in mind and need help figuring out what your solution should look like.</li><li>You have a solid product vision, but don’t know what the team should work on first.</li><li>You have a pretty lean MVP in mind, but aren’t sure how to keep the team focused on just those core features.</li><li>Haven’t had a PM before? <a href="https://medium.com/@erinccummins/10-signs-your-team-is-ready-for-a-product-manager-4ccfe2beb9d3">Check out my list of 10 Signs Your Team is Ready for one here</a>.</li></ul><h4>Project Managers</h4><ul><li>Team members ask what they should work on next.</li><li>Developers are often blocked or waiting for work.</li><li>Team members don’t seem to be working on things in the correct order.</li><li>Team members seem frustrated by frequent changes in direction.</li><li>You have some problems from the Process section above that you haven’t been able to solve on your own.</li></ul><h4>No budget for a PM yet?</h4><p>Create a product roadmap, and make sure your lead designer and engineer are on board and willing to do some management. Efficiency improvements are possible without a dedicated manager, as long as the process is in place.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=af37a2d95171" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 Tips for Product Managers Who Do It All]]></title>
            <link>https://medium.com/@erinccummins/5-tips-for-product-managers-who-do-it-all-96d7185cfe30?source=rss-7a4eda6c9082------2</link>
            <guid isPermaLink="false">https://medium.com/p/96d7185cfe30</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[founders]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Erin C Cummins]]></dc:creator>
            <pubDate>Tue, 26 Feb 2019 16:02:04 GMT</pubDate>
            <atom:updated>2019-02-26T16:02:04.364Z</atom:updated>
            <content:encoded><![CDATA[<h4>Leveraging Agile to Showcase Your Value</h4><p>While not all Product Managers enjoy handling the project management of their team’s software development, I believe this structure has its benefits, especially at smaller organizations. A blended product/project manager can add a lot of value by leveraging Agile, <a href="https://medium.com/@erinccummins/10-signs-your-team-is-ready-for-a-product-manager-4ccfe2beb9d3">freeing up the founder</a> to do what they should be doing — selling the product, scaling the operations, and fundraising. Here’s a handy list to help a reluctant PM showcase their value.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/732/1*9P0G2S3SyytzsMjKmdIK5Q.png" /></figure><h3>1. Efficiency</h3><p>At small, fast-moving startups (with fluctuating priorities), it can be best to have the same person evaluate the change, collaborate with design and tech, propose a solution and schedule the new work accordingly. Remember, this is what Agile was designed for. You’re the expert on the product requirements, UX functionality, stakeholder needs, technical limitations, developer strengths, project timeline, sprint priorities and the longer term roadmap, and are therefore well positioned to make product, priority and project decisions.</p><p><strong>How to</strong>: You can often accomplish collaborations around a sprint change, asynchronously and remotely, within a single ticket shared among everyone involved (and a ping on Slack). Be sure to list any questions you have to help keep the collaboration focused, tag the team members you need, and make sure any deadlines and blocking work are crystal clear.</p><h3>2. Budget</h3><p>Startups often can only afford to hire one person to fill these two roles, and it can be handled efficiently by one person if the development team size is still small.</p><p><strong>How to</strong>: Starting to feel overwhelmed running multiple projects? You can often get help from other team leads on the project management to keep progress moving and blockers addressed while you get your product work done. I’ve had both lead designers and engineering leads help here, and even cover for me during vacation.</p><h3>3. Trust</h3><p>If you’re working at a small startup and are the first PM to join the team, it’s important to remember that the founder was likely directing development themself until you got there. While you build leadership’s trust that you (and future PMs) are going to correctly direct the team on your planned roadmap, it’s going to be easiest for a founder to practice collaborating on product with one key point person.</p><p><strong>How to</strong>: Finding that they aren’t always coming directly to you? Put some process in place for you to proactively collect new requirements before they’re passed to designers or developers. Ask your boss for a weekly one-on-one where you can collect any upcoming new requests. Or, simply Slack them regularly and ask “Anything new coming up that I can help with?” This gives you control over when the conversation happens, rather than it being a surprise interruption.</p><h3>4. Convenience</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*chuXuaPXeCnTm6I_nN0eOw.png" /></figure><p>It’s easiest if the founder and others can come to one manager with feature requests and status questions. Coming to you for everything is much easier than having them figure out what’s a product question and what’s a project question, because the line, as you know, is gray. With direct access to leadership, you have the opportunity to ask questions and understand the background as a part of that same conversation, rather than playing telephone via another manager.</p><p><strong>How to</strong>: Help them see the value of there being one point-person for all projects. Remember, you hold some great information on team progress for a leader working on strategic decisions. Consider providing weekly project summaries that include project status, estimated completion date and any project risks. Being proactive about reporting shows that you have a solid handle on your projects and builds you up as the go-to person for all product development items.</p><h3>5. Quick Unblocking</h3><p>Developers often have questions about implementation. Sometimes these questions open up a rats nest of complexities that will cause you to (1) rethink the feature’s functionality and/or (2) adjust the feature’s priority (or existence) in the sprint. You keep things quick by being the single person in charge of that ticket’s requirements, priority and communication with stakeholders.</p><p><strong>How to</strong>: Remember to breathe! It’s easy to get caught up in the frenzy of needing to unblock your developers ASAP. Take your time and make sure you think through the new solution with team input and understand the implications. Keep a history of confirmed changes in the ticket so that anyone who picks it up has clear requirements, and always make sure corrected designs are attached. QA will appreciate this.</p><p><strong>Extra credit</strong>: Remember to check in with engineering for any new issues that come up. Working closely with the engineers, addressing their concerns and really leveraging their expertise will help you build a great relationship with their team.</p><h3>Conclusion</h3><p>Proactively putting processes in place that make you the go-to person for all product and project requests will keep you organized, make your life easier, and sets you up for a promotion when it’s time to grow the team. Who better to be Director of Product than the person who has been running point, efficiently releasing new features, building strong relationships and sending out a weekly summary?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=96d7185cfe30" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[10 Signs Your Team Is Ready For a Product Manager]]></title>
            <link>https://medium.com/@erinccummins/10-signs-your-team-is-ready-for-a-product-manager-4ccfe2beb9d3?source=rss-7a4eda6c9082------2</link>
            <guid isPermaLink="false">https://medium.com/p/4ccfe2beb9d3</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Erin C Cummins]]></dc:creator>
            <pubDate>Tue, 19 Feb 2019 16:19:19 GMT</pubDate>
            <atom:updated>2019-02-26T16:13:25.214Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ka3ezblRfQ7eGmcYnYoT_w.png" /></figure><p>As the founder, you’ve been doing fine directing your designers and engineers on your own so far. You’ve all been collaborating really well, and you like being able to give feedback every step of the way. Maybe that will continue to work well for a while.</p><p>But maybe it’s occurred to you that you won’t be able to be so involved as you grow. Maybe you’re raising money, and need to answer to your investors on how you’re going to scale as promised. Maybe you just worked a 14-hour day and aren’t sure how to stop doing that. Maybe you recently had a nightmare where you were bottlenecking your development team while you were at an important sales meeting. Let me help you avoid that nightmare —<a href="https://medium.com/@erinccummins/5-tips-for-product-managers-who-do-it-all-96d7185cfe30"> product and project management</a> can help.</p><p>Here are some more signs that your team would benefit from an experienced PM:</p><ol><li>You have a feeling you’re doing too much, but aren’t sure how to implement an Agile development process that lets you step away.</li><li>The people at your organization currently directing design and development need to start spending more time on other things (sales, marketing, fund raising, technical leadership).</li><li>You’ve launched a V1, collected some insights and could use some help figuring out what V2 should be.</li><li>You have a product roadmap, but you don’t know if it’s right.</li><li>You know you should be talking to your customers, but haven’t had time.</li><li>You have a backlog of features tracked in Excel, a Google Doc, email or Slack.</li><li>You need to start releasing roadmap items more quickly, and aren’t sure if that requires more team members or if process improvements would suffice.</li><li>Your software engineers or designers ask what they should be working on, or have a lot of blocking questions during implementation.</li><li>Your team is spending too much time putting out fires.</li><li>When you ask when a new feature is going to be released, nobody knows the answer.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OjUz_8N36hHbC7V-x1nEpA.png" /></figure><p>Additionally, if you have a Product or Project Manager, here are some signs they could use a little extra help:</p><ol><li>Your PM has trouble communicating expectations or delivery dates.</li><li>Your designers or developers still ask you questions about expected functionality.</li><li>The development process isn’t clear and fully documented.</li><li>You have a quality control issue and need help identifying the process failure point(s).</li></ol><p>If any of these sound like something you’re facing, I can help! My targeted, goal-focused engagements can address any of these issues to get your team on track. If you need more oversight, I offer a part time Director of Product service to help lead your team while aiding in your product and staffing strategy — this offers stability, direction and leadership that keeps you in the loop without adding a full time executive that you don’t need quite yet.</p><p>About me: I’m a product manager/director with nine years of experience managing fast-paced, growing tech teams and getting them to release lean, focused software solutions on schedule. I help founders identify opportunities and set goals, and I help their teams implement solutions. I’m based in NYC and have worldwide remote team experience.</p><p>Let me help you and your team — <a href="https://www.linkedin.com/in/erincummins/">connect with me on LinkedIn here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4ccfe2beb9d3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product management: Time blocking for your sanity]]></title>
            <link>https://medium.com/@erinccummins/product-management-time-blocking-for-your-sanity-a1319d807a06?source=rss-7a4eda6c9082------2</link>
            <guid isPermaLink="false">https://medium.com/p/a1319d807a06</guid>
            <category><![CDATA[time-management]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Erin C Cummins]]></dc:creator>
            <pubDate>Mon, 10 Sep 2018 14:04:29 GMT</pubDate>
            <atom:updated>2018-09-10T14:04:29.016Z</atom:updated>
            <content:encoded><![CDATA[<p>Recently, <a href="https://www.reddit.com/r/ProductManagement/comments/96f5pv/mental_health_as_product_managers/">a Reddit post on Mental health as Product Managers</a> inspired me to write about <a href="https://www.reddit.com/r/ProductManagement/comments/96f5pv/mental_health_as_product_managers/e41fgf0/">what I do</a> to feel in control in a busy, fragmented role. After all, the variety is what I love about the job, but that variety can pull you in too many directions, spread you too thin, and keep you from making progress on your most important tasks. I’ve expanded on that post here.</p><p>Background on the problem: The role is designed to be the interface between business objectives and software development. There’s an emotional burden associated with attempting to please all of your “stakeholders” (it’s not possible), and a physical, time-limited challenge of acting as the day-to-day project manager for any software development projects that you’re in charge of. The bundling of the product and project management roles is often the model in smaller organizations.</p><p>You’re expected to collaborate on business solutions, communicate project progress, write requirements for new features, provide feedback on new designs, participate in resource allocation, test delivered development work (and provide quick feedback), communicate with QA and organize releases. Most urgently, you’re expected to do whatever it takes to unblock any stuck development work. This gets easier with experience, since you get better at predicting issues, writing good requirements (resulting in fewer questions), and solving problems before they become emergencies. But sometimes an engineer will pop up with a question about the way a feature should behave (or might need to behave in the future) and you’ll need to stop what you’re doing, think about your customers’ use cases, possibly get in touch with a client, and provide clear direction to the engineer so that they may continue working on the feature.</p><p>And while all of that day-to-day management is going on, you’re also expected to make progress on your own projects: researching and writing requirements for features further down the pipeline, scoping new requests, assisting on marketing materials, meeting with clients, attending meetings about system architecture, attending meetings to review new designs, and maybe even writing proposals with the sales team. (I have a leadership role at a startup, so I touch a lot of different areas.)</p><p>It’s a fun, fragmented, and sometimes very stressful role.</p><p>My biggest challenge is that the interruptions coming from the management of day-to-day projects (thanks, Slack!) can, if allowed, prevent me from making meaningful progress on my longer-term projects. I was able to pinpoint these interruptions as a source of stress. I needed a way to take control of the interruptions so that they could be correctly prioritized among my other goals.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7cHTXKJ2d7iOSupA1iW6kQ.jpeg" /></figure><h3><strong>Time blocking</strong></h3><p>I’ve been testing time blocking as a way to wrangle these interruptions and help me correctly utilize my time, with tasks correctly prioritized by actual urgency and business need. Yes, I make every effort to quickly unblock development work as issues arise, but beyond that I try to avoid interruptions while I separate my time into:</p><ul><li><strong>Inbox screening</strong> / general updates: Run through my inbox and check Slack (15–30 minutes). <strong>This includes writing down and prioritizing the tasks I find, rather than taking care of them immediately</strong>. I do this about three times a day.</li><li><strong>Project management</strong>: Address any open items on a per-project basis (15–30 minutes each). For each of my active software development projects (or clients), I try to use a solid block of time to address any open issues: checking delivered work, prioritizing new bugs, answering questions, reviewing QA feedback, reviewing any new designs, and any related tasks found in the earlier inbox screening. Keeping my head in the same project for a bit lets me complete related tasks more efficiently. Repeat as necessary.</li><li><strong>Product projects:</strong> An hour at a time (ideally) for other projects (research, scoping or writing, for example). These projects should be prioritized in a list somewhere (I like Wunderlist), depending on urgency and value.</li><li><strong>Meetings</strong>: Attend meetings as scheduled (obviously). If you have any pull as to when they’re scheduled, try to group them into a block.</li></ul><p>Finally, I actually write down these blocks of time as a rough schedule for the day first thing in the morning, either in my notebook, or sometimes in my work calendar, to help force myself to stay focused. I find that having a visual that shows me finishing my work at a reasonable time for the day (like 6pm!) motivates me to stay focused and on track. The schedule also acts as a firm set of goals, so that if I get derailed and do end up working late, I know exactly what I need to accomplish (or push to tomorrow).</p><p><strong>Your team will get used to you not answering everything immediately.</strong> Slack’s conversation threads are great for having asynchronous conversations. When an emergency or blocking issue pops up, go ahead and address it, but try not to get pulled into the fray for too long. Go back to your schedule and adjust as needed.</p><p>This method of time blocking has allowed me to give my longer term projects the attention they deserve, rather than reactively allocating a disproportionate amount of energy to all of the “squeaky wheels.” I think the ability to stay focused on important tasks long enough to complete them efficiently has helped me achieve longer term growth while still working reasonable hours. All of the half-done things that were stuck on my to-do list were definitely stressing me out.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a1319d807a06" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[MVP Your Morning Routine]]></title>
            <link>https://medium.com/@erinccummins/mvp-your-morning-routine-e5b5f830250e?source=rss-7a4eda6c9082------2</link>
            <guid isPermaLink="false">https://medium.com/p/e5b5f830250e</guid>
            <category><![CDATA[life]]></category>
            <category><![CDATA[mvp]]></category>
            <category><![CDATA[life-lessons]]></category>
            <category><![CDATA[morning-routines]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Erin C Cummins]]></dc:creator>
            <pubDate>Wed, 28 Jun 2017 16:22:03 GMT</pubDate>
            <atom:updated>2017-06-28T19:27:58.970Z</atom:updated>
            <content:encoded><![CDATA[<h4>Apply Agile to your morning to make time for the most important stuff.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*j5PxvdaFSpCkYXzDrTVRrQ.png" /><figcaption>credit: Trello Blog <a href="https://blog.trello.com/best-productive-morning-routines">https://blog.trello.com/best-productive-morning-routines</a></figcaption></figure><p>As a software product manager, I’m a big fan of the power that Agile has given me to get important things done in a predictable, scheduled and flexible way. Sometimes I even think about the concept of an MVP (<a href="https://en.wikipedia.org/wiki/Minimum_viable_product">Minimum Viable Product</a>, or the core solution to a problem) as it could apply to other parts of my life, so I decided to apply it to my morning routine.</p><p>First, I defined the problem: I’m often late getting out of the house because, as I get ready for work, I find and do a million other things, causing me to leave later than I’d like to and not make time for writing blog posts and doing coding lessons. These extra tasks were cutting ahead of the most necessary tasks I needed to complete, just like how feature creep can blow out any other project schedule.</p><p>Now that I’ve defined the problem, let’s look at the <strong>steps we can take to try to solve it.</strong></p><ol><li>Set goals.</li><li>Set a budget.</li><li>Define an MVP (Minimum Viable Product) solution and acknowledge other nice-to-haves.</li><li>Scope the solution.</li><li>Prioritize “extras” or P2 “features.”</li></ol><p><strong>Goals:</strong></p><ol><li>Leave the house by 9am.</li><li>Have myself ready with a lunch packed (or planned)</li><li>Have the dog taken care of.</li><li>Do a 20 minute coding lesson, if I have time.</li><li>[Insert whatever else you have here. I’ve heard that people with kids have more to do.]</li></ol><p><strong>Set a budget: </strong>How much time do you have to devote to this every day?</p><ul><li>If I leave the house at 9am, I have a budget of about an hour if I’m up and back from my run (if I’m taking one) by 8am.</li></ul><p><strong>Define a solution, or MVP (Minimum Viable Product).</strong> These are the things that are absolutely necessary.</p><ol><li>Shower.</li><li>Do hair &amp; makeup.</li><li>Get dressed.</li><li>Make coffee.</li><li>Eat breakfast.</li><li>Walk the dog.</li><li>Feed the dog.</li><li>Pack lunch, coffee, snacks, kindle, phone, keys, wallet, makeup case.</li><li>Decide whether I’m taking the dog with me to work. This includes checking my calendar for important meetings and evening plans.</li><li>Decide whether I’m biking or taking the train. This requires checking the weather, checking my calendar, making sure I’m wearing the right thing and not taking the dog.</li></ol><p><strong>Acknowledge other nice to haves.</strong> These are likely items that currently distract me along the way to getting out the door. I’ll have to work to not touch these until all the MVP items are complete.</p><ol><li>Clean up after breakfast and clean out the coffee maker. These are pretty high in the P2 list, since it’s certainly not fun coming home to a messy kitchen after work.</li><li>Email — Looking at my email can definitely be a time suck, especially if it pulls me into doing work before I leave. However, it can give me a sense of what I’m getting into for the day. Perhaps instead of sitting down and reading it on my computer, I can quickly scan it on my phone if I have time, or while I’m waiting for the train.</li><li>Brush the dog’s teeth. This is supposed to be done every day, but doesn’t necessarily need to be done in the morning.</li><li>Send out (or get back) the laundry.</li><li>Wash last night’s dinner dishes, if any are still soaking. Maybe this can be lumped in with #1 if there’s time.</li><li>Unload the dishwasher. This has been assigned to my husband.</li><li>Cut nails. This can wait for the weekend.</li><li>Water plants. This can wait.</li><li>General house straightening, like putting away clutter, collecting stray glasses.</li><li>Take out the trash.</li><li>Internet. Do not look at Facebook or the news unless everything else is completely done.</li><li>Set air conditioner timers to come on before we get home.</li><li>Dinner ideas — Sometimes I like to take stock of what’s in the fridge and mentally prepare a dinner plan so that I know whether I should pick something up after work.</li><li>Clean the bathroom — Sometimes I’ll notice that the bathroom as hit peak grime on a weekday and I’ll be tempted to clean it before work. Obviously this can (continue to) wait.</li><li>Do a coding lesson (I like DevSlopes on Udemy).</li><li>Work on a blog post.</li><li>Anything else you like to do? Do you try to set aside time for writing or learning a hobby?</li></ol><p><strong>Scope the MVP</strong>. How long will the core features of this solution take to complete? Right now it looks like my core MVP items are taking up my full hour.</p><p><strong>Total: 58–61 minutes total</strong></p><ol><li>Make coffee — 3 min</li><li>Shower — 15 min</li><li>Hair &amp; makeup — 5 min</li><li>Check weather, decide whether to bike in and get dressed — 5 min</li><li>Walk dog — 15 min</li><li>Feed dog — 2 min</li><li>Make and eat breakfast — 10 min</li><li>Pack stuff — 2–5 min, depending on lunch plan</li><li>Take dog to work? — 1 min</li></ol><p><strong>Prioritize the nice-to-haves</strong> (aka P2 features) so that once I’ve knocked out the core MVP morning items first, you have the ability to intelligently add other tasks in any extra time remaining. It looks like my budget is full, but there’s always a chance I’ll get up earlier, take a day off of running, take a faster shower or take the dog on a shorter walk (if it’s raining).</p><ol><li>If you’re making time to write or learn a new skill or hobby, prioritize that here. Even if you can only give it 15 minutes a day, it’s nice to use your morning brainpower on something for yourself, and you’ll be glad you did a year later when you have close to 100 hours under your belt. This is where I try to get in a coding lesson or brainstorm some blog post ideas.</li><li>Clean up after breakfast and wash any remaining dinner dishes.</li><li>Brush the dog’s teeth.</li><li>Set air conditioner timers to come on before we get home.</li><li>Take out the trash.</li><li>Dinner ideas</li><li>Send out (or get back) the laundry.</li><li>House straightening</li><li>Email — quick inbox check</li><li>All that done? Now we’re free to browse the internet, watch baby animal videos and/or get angry at the world until it’s time to leave.</li></ol><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FclQdqL1M8L5pm%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FclQdqL1M8L5pm%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FclQdqL1M8L5pm%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="327" frameborder="0" scrolling="no"><a href="https://medium.com/media/9437e6078f49326e4a5eed1758f5d66e/href">https://medium.com/media/9437e6078f49326e4a5eed1758f5d66e/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e5b5f830250e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>