<?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 Tucker Sauer-Pivonka on Medium]]></title>
        <description><![CDATA[Stories by Tucker Sauer-Pivonka on Medium]]></description>
        <link>https://medium.com/@tucker-sp?source=rss-1e4060f40b18------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*XXcPTzBeEjvcaZsExl0f3g.jpeg</url>
            <title>Stories by Tucker Sauer-Pivonka on Medium</title>
            <link>https://medium.com/@tucker-sp?source=rss-1e4060f40b18------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 19:24:46 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tucker-sp/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[Tapping Into Your Agency’s Collective Genius]]></title>
            <link>https://medium.com/ideas-by-crema/tapping-into-your-agencys-collective-genius-d8bba1b1932a?source=rss-1e4060f40b18------2</link>
            <guid isPermaLink="false">https://medium.com/p/d8bba1b1932a</guid>
            <category><![CDATA[agency]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[collective-intelligence]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Tucker Sauer-Pivonka]]></dc:creator>
            <pubDate>Thu, 23 Sep 2021 20:57:43 GMT</pubDate>
            <atom:updated>2022-05-02T14:04:11.927Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KIx5FVcNkZMdqOPBUbUuZw.jpeg" /></figure><p>Have you ever felt stuck cycling on an opportunity within your business, seemingly getting nowhere? Have you tried to connect with one of your agencies on exploring these opportunities within the business, even though it might not be within their realm of work?</p><p>Agencies are chock-full of creative minds. Minds that are continually finding new ways of working, thinking, designing, developing, testing, managing, marketing, and so much more. <strong>Why is it that clients don’t capitalize on these teams of diversely brilliant individuals to help solve business problems beyond the work they were directly tasked with completing?</strong></p><p>While there are some agencies out there that aren’t looking to go above and beyond their assigned work, partnership-driven agencies would jump at the opportunity to help a client work through a unique business problem that goes beyond the assigned work. Partnership-driven agencies, such as <a href="https://www.crema.us/">Crema</a>, jump at this opportunity without worrying about ‘selling’ the client on the work and instead investing further into the relationship on their own fruition.</p><h3>Take advantage of the team’s broad experience</h3><p>Imagine the potential of what you could achieve by tapping into the collective genius of your agency partner.<strong> </strong>How would your business change if you were able to tap into staff that has experience and immersion in other verticals, types of work, and organizations beyond your reach? The best agencies can take this broad experience and match it exactly with the client’s needs. That’s why we solve problems differently.</p><p>When you or your business are stumped on a problem, even if it seems completely irrelevant to the work your agency is doing, chances are you’d get some fresh ideas if you presented your agency team(s) with the problem. These agencies can help unlock your team; understand your problems in new and interesting ways; evaluating the hard decisions that you face; and work to get you a jump start.</p><h3>Agency staffing presents the opportunity for problem solving</h3><p>When agency employees get pulled into a new problem to solve that’s outside of their day-to-day, the excitement is palpable. These are often great opportunities for agencies to introduce other great minds that may not be directly allocated to your work.</p><p>These types of requests are also likely to get the attention of the agency leadership team, who are often working to find new ways to provide value to clients beyond the work that their teams are directly providing.</p><p>Not only are you getting some fresh minds on your problem, but you’re also getting an experienced leadership team that has collectively worked with hundreds of clients, working to solve the problem their past clients experienced. Why not use this experience to pull from problems that have already been solved?</p><h3>How to creatively utilize the full potential of your team</h3><p>There are so many ways you can harness your team’s genius. The sky’s the limit! Here are some signs that you could benefit from your agency partners and ways they might help.</p><p><strong>Your leadership team is going in circles on a topic that has spanned multiple meetings.</strong> Ask your agency if you can pull in a team member that’s familiar with your business to provide a different perspective to the group on the problem. It might be entirely unrelated to their direct work, but they’re familiar enough to maybe call out a solution that the leadership team is way too close to see themselves.</p><p><strong>You’re trying to figure out which new piece of software to invest in that allows for better tracking of work within your business.</strong> The team members at your agency have probably worked with multiple project management software solutions. Reach out to them to ask for their recommendations.</p><p><strong>You are looking for a subject matter expert (SME) in a seemingly unrelated area to your agency to provide input on a plan or a presentation. </strong>Your agency can make a call out to the entire company in a public chat channel asking if anyone has any experience with X. If someone in the agency has deep experience in that particular area, you’ve just gained access to a new level of expertise.</p><p><strong>You have an idea, but you’re not sure how to sell it to your business partners. </strong>Tap into your agency because they’re <em>very</em> used to selling ideas. This is right up their alley to unpack this alongside you and advise you how to format your deck and what content to focus on.</p><p><strong>Are you trying to hire your own team? Are their roles that are similar to roles at your agency?</strong> Ask them if they have job descriptions you can borrow, or even review the job descriptions you have to see if they have any feedback. What about having a few trusted team members at the agency join the final interview to provide you with their feedback?</p><p><strong>You need to write a new data retention policy, and you’re not sure what the best practices look like for these.</strong>Your agency has folks on staff who either have experience in writing these or at least can advise you on some things to consider and point you in the right direction. 30-minute meeting max.</p><p><strong>Your team is looking for ways to serve its customers beyond its current offerings</strong>. This is a perfect opportunity to bring in an outside team who knows your business well, but hasn’t been permitted to explore possibilities directly with you.</p><h3>What is and isn’t acceptable to ask</h3><p>Some agencies look at client requests as something that may distract the team, increase the workload, introduce too big of expectations, or even create risk. Spoiler alert: These agencies aren’t looking to help your business thrive, instead, they are focused on their bottom line and their own success over yours. That shouldn’t be the case in a <em>great</em> agency relationship.</p><p>Partnership-driven agencies want to help your business succeed. They know by being there to help you solve some of your greatest challenges, the work will continue to flow, and may even grow as they gain your trust. This is why they’re often willing to do this type of work at no additional cost to you — it’s an investment for them, just as you’re investing your business’s dollars into their work.</p><p>Great agency relationships should allow room to explore other problems you have in your business. <strong>This doesn’t mean you should distract your team away from their work regularly, as that would create issues with delivery. </strong>But I’m willing to guess that if you have enough consistent problems to pull your team, it’s likely a project that’s important enough to give the dedication of time and money.</p><p>There might be people inside your agency that specialize in a sort of problem. Working with this team will keep the main team focused but able to support.</p><h3>Wrap up</h3><p>Next time you’re stuck, experiencing a problem, need a subject matter expert, or would just like a fresh perspective on something, think about connecting with your team at your agency. See if it’s possible to pull in someone to a meeting that’s completely outside the context of their work with you.</p><p>Trying this experiment will quickly tell you what type of agency you have retained; a great agency, or an agency that’s watching out for their bottom line over your success. This is the bar that agencies should be working to reach, not just doing the bare minimum. Great agency partners care as much about your success as you do.</p><p>Next time you’re finding yourself cycling on a problem, reach out to your agency to see how they might help you move the ball forward in a creative way.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d8bba1b1932a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ideas-by-crema/tapping-into-your-agencys-collective-genius-d8bba1b1932a">Tapping Into Your Agency’s Collective Genius</a> was originally published in <a href="https://medium.com/ideas-by-crema">Ideas by Crema</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Power of Partnering with an Agency to Extend Consulting Services]]></title>
            <link>https://medium.com/ideas-by-crema/the-power-of-partnering-with-an-agency-to-extend-consulting-services-b981248d74f6?source=rss-1e4060f40b18------2</link>
            <guid isPermaLink="false">https://medium.com/p/b981248d74f6</guid>
            <category><![CDATA[process]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[product-team]]></category>
            <category><![CDATA[consulting-firms]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Tucker Sauer-Pivonka]]></dc:creator>
            <pubDate>Mon, 05 Apr 2021 15:13:39 GMT</pubDate>
            <atom:updated>2021-04-05T15:15:36.159Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Originally posted at </em><a href="https://www.crema.us/blog/the-power-of-partnering-with-an-agency-to-extend-consulting-services"><em>Crema.us</em></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O_uh4JnW3VroiFOVyRXQjQ.png" /></figure><p>It’s no secret that working at a consulting firm can be challenging, no matter the specialty. The firm is being hired to solve some major problems that their client’s business is facing. Oftentimes, solving these problems requires an astronomical amount of people hours spent analyzing information, finding applicable benchmarks, and working to ensure that whatever the firm recommends, it’s the best possible approach.</p><p>The smart folks that join these firms do so because they love problem solving. Each new client brings an interesting new challenge that is just different enough from the past work to make it exciting. However, all too often, these consultants are spending hours upon hours doing work that can be made easier with software. Instead of using their experience and expertise, they end up spending a large portion of their time going through manual processes, which may ultimately lead to burnout due to a general lack of fulfillment in their day-to-day work. Investing in internal efficiency software can be <a href="https://www.crema.us/blog/digital-generosity-pt-1-how-internal-software-can-help-employees-feel-fulfilled">a generous act</a> for your employees on the ground, as it’s ultimately helping create less friction, allowing them to do their job more effectively.</p><p>In addition to that, having a good reputation isn’t always enough in this day and age when pitching new clients. Clients are wanting more. They know they have many options and they want to understand what makes one firm different from the other. Of course, sometimes this can be like comparing apples to oranges, but when a potential client is trying to make an apples to apples comparison, having software assets that allow you to serve your clients more effectively, may just be the edge you need to beat the competition.</p><h3>Validating Ideas</h3><p>Many consultancies already have validated some form of an idea of what they could build. Often, this is informed by associates in the day-to-day trenches; The folks that have created impressive Excel macros, move across storage systems at the speed of light gathering relevant information, and create pages or slides that distill all of that information into something digestible by the client.</p><p>This does the trick for a long time, but the context of how all these tools and tricks work together is often locked away in their brilliant minds. What happens when that person leaves? The next person needs to scramble to figure out how the last person was doing the work or — even worse — they miss something critical and it misinforms a key strategy.</p><p>Excel models and PowerPoint decks are great tools for a reason. They do the job well. Many times, these Excel models serve as the initial prototype of an idea. They validate the solution, even if it is only within Excel. Once patterns begin to emerge from the work and processes, there’s a great opportunity to build software around those patterns to allow the consultants to work more effectively and efficiently. Not only does this help the consultants from an efficiency standpoint, but it creates less room for human error when they’re moving at the speed of light to prepare for a client presentation.</p><h3>Partnering</h3><p>Now the firm needs to find someone to help build upon this idea. Do they hire? Or do they partner? While some consultancies have product-focused business units, they may also want to mitigate their risk by bringing on staffing that’s not fixed, rather than ramping up staffing on their own, or having to wait until there’s room on the roadmap to fit their priorities in. Instead of having to hire and manage a product team (or multiple product teams) it may be a better business decision to bring in a partner that provides a variable cost to the business.</p><p>Consultancies understand the value of bringing in outside assistance to solve business problems of their own. They understand their strengths and weaknesses, so partnering with a product agency like Crema, isn’t a new concept to them. They come to the table being experts in their space, and we can come to the table being experts in using technology to solve the problems they’re experiencing.</p><p>We do our best work when someone within the consultancy is a designated product advocate; someone to own the decision making, but also champion the solution(s) internally. Generally, this person is well connected in the organization and knows who’s shoulder to tap to gain more information about a particular topic when needed (e.g., how we serve clients on x types of studies).</p><p>Sometimes, the product advocate may not be able to make the decision to bring on a new partner, or to make this large of an investment. If you’re finding yourself in that scenario, it may require some extra due diligence on your part to (1) identify the key problems that need to be solved and (2) pitch possible solutions to your leadership. Once alignment is established, you can begin the hunt for choosing a product agency.</p><p>It’s not enough to bring in a vendor to do the work, but instead to <a href="https://www.crema.us/blog/what-to-watch-for-when-choosing-a-digital-product-agency">bring in a partner</a> that will act as an extension of their team; someone who’s going to be invested in solving the right problems, and not just taking order; someone who’s going to challenge the assumptions and provide alternative solutions; someone who’s going to allow the organization to level up their services through innovation and technology. We’ve created <a href="https://assets.website-files.com/5b6b50e79e9b6f5948395973/5ffc786640c01bbc43d96d30_Choosing%20a%20Digital%20Product%20Agency.pdf">a guide to choosing a digital product agency</a> to help you navigate the search.</p><h3>Gathering Buy-In</h3><p>If you have identified a product advocate in your organization (or maybe you’re the advocate), the next step is to gather buy-in from your team. The solution will only be as good as its usage. If you don’t gather enough buy-in, you will have built this fancy product that no one uses. This is often the stage that’s easiest to get stuck in, but after years of working with consultancies, we’ve identified what works well to ensure usage remains high.</p><p>The consultants will often defer to their typical processes any time something doesn’t work exactly as expected — understandably, they need predictability. However, products are built incrementally, so there’s a balance to be found that helps them, but doesn’t slow them down.</p><p>So, as you begin exploring a new solution, it’s incredibly important to interview and understand how folks on the ground level are doing their work. What’s most important to them? What’s one piece of functionality that could be built that would maybe save them 5% or 10% of their time? Through these interviews you’ll learn what the actual problems are that need to be solved, rather than just doing what the leaders in the organization <em>think</em> need to be solved for. You’re also bound to generate some excitement from some of them. Take note of that so that you can come back to them and create product evangelists out of them. They can quickly become influencers on the ground level and help mitigate reservations about the new product amongst their cohort.</p><p>When creating a new product (especially in this space), the first [few] increments should prioritize internal value over client-facing features. By delivering value internally first, you ensure that it will actually be used with clients once you roll out the client-facing features and/or product(s). This is important to not lose sight of, because if your ground-level folks aren’t using the tool, the clients won’t see it and the product will begin to gather dust, leading to a loss on the investment.</p><h3>Summary</h3><p>Providing clients with a well-polished digital user experience goes beyond the stereotypical pages or slides that get presented to a client and allows the client to interact with the insights and recommendations in real-time. No longer do they have to wait for a big reveal. Instead, they can view work happening in real time, and the information can be dynamically updated as business conditions change without needing an associate to manually process those conditions. This can open up additional opportunities to capture revenue for consulting firms, ultimately opening up their consultants time to serve more clients well.</p><p>When thinking about building a solution, always remember your internal groups first and the costs saved there. If you can make your consultants’ lives 10% easier through technology, not only will you save on the hard costs of that time, but they will likely stick around longer and build stronger relationships internally and externally to help your business thrive.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b981248d74f6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ideas-by-crema/the-power-of-partnering-with-an-agency-to-extend-consulting-services-b981248d74f6">The Power of Partnering with an Agency to Extend Consulting Services</a> was originally published in <a href="https://medium.com/ideas-by-crema">Ideas by Crema</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Fostering Psychological Safety & Constant Improvement as a Product Manager]]></title>
            <link>https://medium.com/ideas-by-crema/fostering-psychological-safety-constant-improvement-as-a-product-manager-7cd6edb790cf?source=rss-1e4060f40b18------2</link>
            <guid isPermaLink="false">https://medium.com/p/7cd6edb790cf</guid>
            <category><![CDATA[psychological-safety]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[improvement]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[team-building]]></category>
            <dc:creator><![CDATA[Tucker Sauer-Pivonka]]></dc:creator>
            <pubDate>Mon, 20 Jul 2020 22:04:18 GMT</pubDate>
            <atom:updated>2020-07-21T17:26:30.265Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*YeSnCBwFfbdLH2ZE1MgXfw.png" /></figure><p>Product managers know — or a have likely heard — that psychological safety is an important element to their jobs. The concept has risen in popularity over the past several years as organizations are focusing ever more intently on culture and the work environment. But what does it mean or look like in practice for product managers? What’s the <em>real</em> value of psychological safety?</p><p>Aside from the necessity of creating an environment where team members feel secure and accepted, psychological safety allows for a myriad of additional benefits for product teams (and really any kind of team for that matter). One of the most significant being that it gives teams the encouragement and space to continually improve in their craft.</p><h3>So, what is psychological safety?</h3><p>Before going any further, let’s take a look at the original meaning of the phrase, coined by <a href="https://www.hbs.edu/faculty/Pages/profile.aspx?facId=6451">Amy Edmondson</a>, the Novartis Professor of Leadership at Harvard Business School. In her <a href="https://journals.sagepub.com/doi/abs/10.2307/2666999">research</a>, Edmondson describes psychological safety as, “a shared belief held by members of a team that the team is safe for interpersonal risk taking.”</p><p>It’s about whether you feel safe enough to ask potentially “silly” questions. Or if you feel comfortable to ever fail or admit a mistake. Ultimately, it’s about making sure there is a healthy level of comfort for everyone on the team to thrive.</p><p>Edmondson’s definition proposes that psychological safety is experienced at a team level rather than individual, which presents an opportunity for product mangers. Because PdMs (product managers) oversee, protect, and advocate for all the members of the team, they are in a unique position which allows them to lead the charge for a more psychologically safe team dynamic.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VNratbDTsOkIA_cB.png" /></figure><h3>Fostering psychological safety on your team</h3><p>It starts with <em>you</em> as the product manager! Or the person on the team who has taken on the initiative to cultivate this type of environment. There are many tactical boxes you can check for psychological safety on teams, but how you actually interact with others is what will set the expectation for the entire team.</p><p>This could mean starting every conversation with a perspective of empathy and understanding that the team member you’re working with has things going on in their own life. If you can create a safe environment, then everyone can move forward together regardless of what else is happening outside of work.</p><p>You can hope and encourage others to push for a healthier team dynamic, but you serve as an example that others on your team will take from. Don’t be afraid to admit failure yourself. It will show the rest of the group that small mistakes are okay. They actually often lead to learning!</p><h3>Encourage and assist others on your team to continually improve</h3><p>Once a team climate of mutual respect and acceptance has been established, each of the individuals of the team can bring their fully authentic selves. This puts the team in a position most conducive to learning, as there is less risk or fear of judgement. When the team isn’t afraid of failure, real growth and innovation happens!</p><p>Imagine a work environment where you can ask all of the questions you have, confide in others about the mistakes you’ve made, and pitch your wildest ideas without the risk of reproof. Imagine the possibilities for breakthroughs and overall team improvement.</p><p>It also becomes easier to encourage your teammates to invest time and effort into specific areas for improvement. As a product manager, you are in a special position to open up respectful, helpful dialogue to assist them in finding opportunities to learn. You’re not their manager or an equal in their field, but you are working with them regularly managing the product they work on. This presents an incredible opportunity to present feedback in a non-threatening way.</p><p>Take on the role of being their cheerleader! Others generally know where they need to improve or the path they want to go in terms of professional development. It’s not only valuable for that team member, but for the whole team to get closer together and figure out new ways to collaborate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Ed1ashY-M55vUFUK.png" /></figure><h3>Prepare for difficult conversations to protect and advocate for a psychologically safe environment</h3><p>It’s going to happen at some point in your career as a PdM. You, or someone on your team will unknowingly create friction or discomfort for others by their actions. It might be a client, another team member, an outside vendor, etc. that says or does something that comes across in a harmful manner. Assume that it’s going to happen, but also work to assume the best intent in others.</p><p>This is not to say that feelings and issues are to be ignored. Sometimes it does take an apology which can be extremely difficult, but necessary. Addressing the issue is the best thing you can do to help everyone move past it and ensure that it won’t happen again. Have the conversation with your team and do your best to create an environment that is psychologically safe.</p><p><strong>Check out the </strong><a href="https://www.youtube.com/watch?v=geqX16HekCI"><strong>Product Manager Round Table</strong></a><strong> live video for a more detailed discussion on this topic and more.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7cd6edb790cf" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ideas-by-crema/fostering-psychological-safety-constant-improvement-as-a-product-manager-7cd6edb790cf">Fostering Psychological Safety &amp; Constant Improvement as a Product Manager</a> was originally published in <a href="https://medium.com/ideas-by-crema">Ideas by Crema</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Create an Agile Team Working Agreement]]></title>
            <link>https://medium.com/ideas-by-crema/how-to-create-an-agile-team-working-agreement-7bc98df008a1?source=rss-1e4060f40b18------2</link>
            <guid isPermaLink="false">https://medium.com/p/7bc98df008a1</guid>
            <category><![CDATA[teams-and-teamwork]]></category>
            <category><![CDATA[product-team]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Tucker Sauer-Pivonka]]></dc:creator>
            <pubDate>Fri, 21 Feb 2020 19:59:47 GMT</pubDate>
            <atom:updated>2020-02-21T20:00:38.007Z</atom:updated>
            <content:encoded><![CDATA[<h4>Documenting implicit team norms in an explicit and collaborative manner</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YLBelg7K1nzQh1QtEnThdA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@youxventures?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">You X Ventures</a> on <a href="https://unsplash.com/s/photos/team?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>An agile team working agreement is essentially a document that lists out a team’s norms using statements like “We value long-form asynchronous communication over short, unclear messages.” These documents are a way to take implicit agreements and make them explicit so that the team can remain aligned throughout the duration of a project. This can be a particularly useful tool when a new team is spinning up and norming together.</p><p>There are many different articles online about the ‘right’ way to create an agile team working agreement, but I find that it’s best to come up with a process of creation that works well for your team and your culture. Earlier this month, I facilitated a session that worked extremely well for that team, but it’s not to say that way would work for everyone. However, you should be able to take the principles from this post and apply it to your team.</p><h3>When to Create an Agile Team Working Agreement</h3><p>The short answer to ‘when should my team create an agile team working agreement’ is <em>now</em>, (if you don’t already have one). However, the <em>best</em> time to create these agreements is at the very beginning phase of a project, especially if it’s a new team. It’s most critical at this time because the team may have preconceived notions of how the team will work. I have found that this is also a great time for a team to begin having some healthy debate. It breaks down that wall early on in the project lifecycle, so that the first issue they disagree on in the project isn’t the first time they’ve had to debate one another.</p><h3>How to Create an Agile Team Working Agreement</h3><p>The creation of an agile team working agreement should be a collaborative process. As I’ve mentioned earlier, there are many ways to do this, and I’m simply describing a way that has worked well for our teams. When thinking about the facilitation of this process, ask yourself, ‘what is your team most comfortable with in terms of collaboration?’ At Crema, it’s now a norm that we use a virtual whiteboard (even if no one is joining remotely), called <a href="https://miro.com/">Miro</a>. Using a product like Miro can be helpful because of the wide variety of features such as voting, reacting, timers, etc. However, you could use a collaborative document like Dropbox Paper, regular sticky notes, or even use a physical whiteboard to anchor discussions. It’s really up to you.</p><p>The first step in this process is setting the scene for your team. Give them an explanation of why this document can be valuable to them, as well as what the process is going to look like. Then, kickoff the process! Ask the team to answer the following question: <em>What are the decisions that, if made now, could help us in the future when the pressure is on or things haven’t gone our way?</em></p><p>Then, set a timer for about five minutes and ask the team to generate as many ideas for working norms as possible. This is a good time to remind them to think of the agreements as ‘We believe…’ or ‘We value…’ statements to avoid having to clean things up later.</p><p>After the time is up, take some time to review all the sticky notes as a team. Ask the team to call out any clarifications that they need to understand what the sticky note means, <strong>but not to discuss it yet</strong>.</p><p>Once the entire team is clear as to what each sticky note means, ask them to rate each norm using the following scale. Thumbs up ( 👍🏼 ) for full agreement, neutral face ( 😐 ) for questions, or thumbs down ( 👎🏼 ) for disagreement. Here’s the catch with disagreeing though; If anyone disagrees, they have to suggest something better.</p><p>Once the team votes, review all the new norms. Anything with all thumbs up immediately becomes a new norm. Anything with a neutral face should be discussed further. Once the team aligns on it (including rewording), then it becomes a norm. Any norm that includes a thumbs down should be discussed and decided if it should be thrown out or revised to work with the team.</p><p>If you use the method described above, you will likely end up in a scenario where there are duplicates. Work to consolidate them into common themes and ask the team about suggestions for rewording that align the near-duplicated sticky notes. At this point, you should have a set of new team norms that can be placed into some kind of public document that is referenced on a regular basis. All of our ‘final’ documentation at Crema is placed in <a href="https://www.atlassian.com/software/confluence">Confluence</a> for future reference, but this could be any repository of documents that makes sense in your organization. What’s important is that people know where it lives.</p><h3>What’s Next?</h3><p>After you’ve created this agile team working agreement, it’s important that it’s not forgotten about. It should be a topic of conversation on a regular basis. Depending on your process, this could look different, but a bi-weekly retro would be a great time to check in to make sure everyone feels like the norms still represent the team. It’s perfectly okay if the norms need to be adjusted to better fit the team as the project progresses and the team learns how to work well with one another. If the team values constant improvement, there should be no problem discussing changes and/or calling team members out when they’re breaking the agreement, especially since the entire team agreed to this collaboratively.</p><p>I hope you’ve found this overview of agile team working agreements helpful. If you have any questions, comments, or even arguments against it, I would love to hear them.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7bc98df008a1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ideas-by-crema/how-to-create-an-agile-team-working-agreement-7bc98df008a1">How to Create an Agile Team Working Agreement</a> was originally published in <a href="https://medium.com/ideas-by-crema">Ideas by Crema</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Write User Stories]]></title>
            <link>https://medium.com/ideas-by-crema/how-to-write-user-stories-fdc3746d59c?source=rss-1e4060f40b18------2</link>
            <guid isPermaLink="false">https://medium.com/p/fdc3746d59c</guid>
            <category><![CDATA[process]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[user-stories]]></category>
            <category><![CDATA[scrum]]></category>
            <dc:creator><![CDATA[Tucker Sauer-Pivonka]]></dc:creator>
            <pubDate>Thu, 21 Feb 2019 17:10:56 GMT</pubDate>
            <atom:updated>2019-10-09T19:04:40.302Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FrDceIp-Kg1_gi8QKNYvYA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/gNUMZjxd89w?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">rawpixel</a> on <a href="https://unsplash.com/search/photos/agile?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>User stories largely take place of the <a href="https://www.bmc.com/blogs/software-requirements-specification-how-to-write-srs-with-examples/">traditional requirements documentation</a> you see in more of a <a href="https://en.wikipedia.org/wiki/Waterfall_model">waterfall type</a> environment. They are used as a way for the product team to understand the user persona and the ultimate goal, but leaves enough room for the product team to come up with the best solution based on <em>their</em> expertise.</p><p>A user story may be represented in various ways to ensure your team can deliver their best results. The main thing to take away from this post is that the process police won’t come find you if you’re not following these methods exactly. At the end of the day, <strong>the most important thing is that your team has enough autonomy to make their own decisions within the guardrails you and the rest of the team outline.</strong></p><h3>What type of work falls under ‘user stories’?</h3><p>User stories can be used for almost any kind of product development; From design to development and even testing, it’s flexible enough to speak to any one of those individual groups. Traditionally, you’ll find that users stories cover the entire solution from beginning to end and include everything from design to testing, but we have found that it’s not always the most <em>practical</em> way to get the work done. So, we typically break out the design tasks from the development and testing tasks, as design typically leads in terms of progress.</p><p>Some other work that is inevitable, but may not fall under the structure of a user story for your team, could be referred to as ‘Chores,’ ‘Design Tasks,’ ‘Tests,’ etc. The separation of this work into various task ‘types’ allows for adjustment of your workflow based on the type (e.g., Chores, Design Tasks, etc.). This is largely specific to how you and your team function, but can be helpful when you have different work streams going on (e.g., working on validating a high-fidelity design prototype while the development team is working on features that have already been validated).</p><p>This section wouldn’t be complete without talking about how User Stories connect to the bigger picture. Most often, user stories are linked to larger initiatives called <a href="https://www.crema.us/primer/epics-stories">Epics</a>. Epics are the highest-level of organization for agile tasks. Most often, Epics are features, whereas User Stories and other linked tasks are the tasks that have been broken down to complete that feature. However, different software solutions may even allow you to break things down more granularly, such as Epic -&gt; Features -&gt; Stories -&gt; Sub-tasks.</p><p>Typically, Epics are what’s shared on a roadmap, and the stories and other related tasks are what determine how long it will take to complete that Epic (usually based on story points). An example of an epic could be ‘User Login’ and all user login based tasks/stories/chores could fall underneath that epic.</p><h3>The Format of a Good User Story</h3><p>It’s important that when you adopt user stories as part of your process that you go ‘all-in’ and ensure that they are structured in a way that allows your team to do their best work. User stories aren’t any good if they lack the necessary and/or relevant information the team needs to actually complete the work that your client and/or stakeholders are expecting.</p><p>Each user story I create typically involves the following parts:</p><ul><li>Title</li><li>Overview</li><li>Acceptance Criteria</li><li>Reference &amp; Considerations</li></ul><p>Other elements that are involved in the process:</p><ul><li>Testing Instructions (Provided by Developers)</li><li>Testing Verification Details (Provided by Test Engineers)</li></ul><p>Now, let’s break down each of those parts.</p><h3>Title</h3><p>While agile based software has made all of our lives easier, I haven’t found software that makes it easy to scan for particular stories using a traditional story format method within the title field (e.g., As a x user, I want x, so that I can x). So, instead of including the ‘story’ part of the user story within the title field of a task, I typically create a shorthand so that it’s easier to find what you’re looking for at a moment’s notice. What this ultimately looks like is:</p><p>Title: <em>Login | Forgot Password</em></p><h3>Overview</h3><p>Now that we have the title out of the way, it’s important to provide the team the context they need in order to come up with the best solution. This section should include <em>just enough</em> information for the team without prescribing a solution.</p><p>While some feel very strongly about following the traditional user story formula (e.g., As a regular user of product x, I need to be able to retrieve a new password in case I forget my password, so that I can log back into product x.’), I don’t think it’s 100% necessary to follow that exact format. What is important though, is that you stick with whatever format you choose to create consistency and predictability for the team on what they should expect for each user story. Using the example above, if I were to create this story I would probably just summarize a bit more to be something like:</p><p><em>Users need to be able to securely reset their password in the event that they forget their password.</em></p><h3>Acceptance Criteria</h3><p>Ah! Arguably the most important part of the user story. This is the part where things can become a little <em>too</em> prescriptive if you’re not careful. Remember, your goal is to communicate the needs to the team, without directly prescribing a solution (unless 100% necessary).</p><p>Here’s the thing about that though — this requires that you to have a team of mature contributors. If you’re starting with a brand new product team, it might require you to be a little more prescriptive until trust has been gained amongst the team.</p><p>Using the basic example we’ve used throughout this article, the acceptance criteria I would include for this story would look something like this:</p><ul><li><em>Users are able to securely reset their password</em></li><li><em>Once the user has reset their password, the user should be able to log back in using that new password</em></li></ul><p>What’s important to note about the above criteria is that it (1) doesn’t prescribe if we should send an email, utilize secret questions, or utilize some other kind of (secure) authentication method to help the user reset their password or (2) it doesn’t say how this should look. Those details should be worked out among the product team so that they implement the best solution based on their expertise or the organization’s broader guidelines. Now, if you have some very specific requirements like ‘a user may only to request to reset their password two times in 60 minutes,’ that could be another acceptance criterion. Or, if this flow has already been created within the design prototype, you could include a criterion that states, ‘The forgot password flow should match the flow outlined within the prototype.’</p><h3>Reference and Considerations</h3><p>This section is great for keeping track of relevant information that isn’t necessarily requirements, but still important for the team to know (e.g., reusability will be key, as there are high-level business conversations around building this functionality out further). This section is also where I link all necessary support materials, such as the link to the prototype, necessary API documentation, etc.</p><p>Using the example above, assuming the designs do not exist, I would include the following:</p><ul><li><em>Work with Designer X to determine the best possible user experience for the forgot password function</em></li><li><em>Please keep in mind that some regular users have 2FA enabled. They should have to enter their 2FA information before proceeding to reset their password.</em></li><li><em>Consider including some kind of captcha service to avoid people trying to use brute force to gain access.</em></li></ul><p>Most often, I use this section to just include a link to the necessary screens in the prototype, as well as any ‘nice to have’ type of functionality.</p><h3>Testing Instructions and Verification</h3><p>Within our user stories, this typically isn’t part of the main story description, but instead included as links to documentation within specific repos and associated to a PR (pull request). The testing instructions give the other developer(s) reviewing a PR specifics on how they should verify that work, as well as the Test Engineer. Additionally, by separating the testing instructions out, it keeps the original story ‘pure’ while maintaining all relevant documentation in once place. On several of Crema’s product teams, the developers own adding the testing instructions. However, if you have specific flows you want to ensure get tested, I would encourage using your reference/considerations section for that.</p><p>Additionally, our Test Engineering team always adds a verification to each task tested. This includes relevant info such as what browser(s) they tested with, along with the version, as well verification that each piece of acceptance criteria passed or failed the tests. If anything fails, it goes back to ‘To Do’, but if it passes, it moves to ‘Done.’ This helps hold everyone accountable, but can also serve as quick documentation for DevOps teams if they must verify all tasks are tested before a release.</p><h3>Who You Need to Involve in User Story Creation</h3><p>Hands down, the best way to create user stories for your team is to involve them in the process. This is often done using a process called ‘Story Mapping.’ Story mapping is a way to visually map out the user journey, and then collaborate on the acceptance criteria to ensure no stone goes unturned and that your stories are written at the appropriate level of granularity. Not only is this process helpful to ensure you capture all the nitty gritty details and come up with the best solution, but it also holds everyone accountable, including your clients (as long as they’re involved). This helps ensure that surprise requirements don’t come up as frequently, or when they do, it’s more clear that it’s a brand new story.</p><p>This isn’t an article about how to run a Story Mapping ceremony though. You can find more information on the topic <a href="https://agilevelocity.com/agile-tools/story-mapping-101/">here</a>.</p><p>So, running a story mapping ceremony for every single thing you and your product team works on may not be the most efficient process in all cases. While I certainly encourage the use of this for large feature sets (e.g., breaking down epics), sometimes you just need to create a few user stories without getting the entire team together. If this is the case, what I’ve found works best is to create the user story/stories and then run those by the team asynchronously or during one of your sprint kickoff ceremonies. Either path you choose, it’s important to get buy-in from your product team on them before proceeding.</p><h3>Summary</h3><p>Hopefully this article has shed some light on one of the ways Crema goes about writing its stories. If this process isn’t new to you, what are some ways that you’ve had success with the creation and implementation of user stories? Do you have any processes that have proven to be even better than what’s listed above? If so, leave a comment below! I’d love to hear from you!</p><p><em>Originally published at </em><a href="https://www.crema.us/blog/how-to-write-user-stories"><em>www.crema.us</em></a><em>.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F3eee85%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2F3eee85&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/649b83359ed6c72f505d9bd1d5e9ed30/href">https://medium.com/media/649b83359ed6c72f505d9bd1d5e9ed30/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fdc3746d59c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ideas-by-crema/how-to-write-user-stories-fdc3746d59c">How to Write User Stories</a> was originally published in <a href="https://medium.com/ideas-by-crema">Ideas by Crema</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What’s the Difference Between Kanban and Scrum?]]></title>
            <link>https://medium.com/ideas-by-crema/whats-the-difference-between-kanban-and-scrum-647dec826a20?source=rss-1e4060f40b18------2</link>
            <guid isPermaLink="false">https://medium.com/p/647dec826a20</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[kanban]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[jira]]></category>
            <dc:creator><![CDATA[Tucker Sauer-Pivonka]]></dc:creator>
            <pubDate>Thu, 31 Jan 2019 21:05:23 GMT</pubDate>
            <atom:updated>2019-10-09T19:05:05.352Z</atom:updated>
            <content:encoded><![CDATA[<h4>Which framework should you use for your next project?</h4><p>Do you find yourself asking which agile framework to use? Do you think Kanban and/or <a href="https://www.crema.us/primer/scrum">Scrum</a> sound like some kind of strange dessert? Well you’ve arrived at the right place! Crema employs both of these agile frameworks, and sometimes even a mixture of them to produce the best results for our clients. Within this post you’ll find the definition of Kanban, Scrum, pros and cons of each, mixtures of the two frameworks and even suggestions on which to use for your next project.‍</p><h3>What is Kanban?</h3><p>Kanban in its simplest form is a way to manage work by weighing <a href="https://www.techopedia.com/definition/13935/change-request">requests</a> with capacity. This <a href="https://www.crema.us/primer/agile">agile</a> framework originated from lean manufacturing, most widely associated with <a href="https://en.wikipedia.org/wiki/Lean_manufacturing#Toyota_develops_TPS">Toyota.</a></p><p>The largest visual differentiator between Kanban and Scrum is the lack of <a href="https://www.crema.us/primer/sprints">sprints</a>. Typically, Kanban boards are organized into columns and the work flows from left to right. The left most column is typically work to be done and the right most column is the work that has been completed, or sometimes, blocked. It’s important to note that there’s no right or wrong way to setup a Kanban board and that it greatly depends on a variety of factors such as the type of work being done, restrictions imposed by process, the inclusion of <a href="https://www.crema.us/primer/epics-stories">epics</a>, etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-WYIDPtZiUKBvKtx.png" /></figure><p>While Kanban has become popular with software development, it’s also becoming more and more popular with other business aspects such as recruitment, marketing projects, and leadership initiatives.</p><p>The primary metric used within Kanban to determine process effectiveness is cycle time, though, that metric isn’t used by all.</p><h3>What is Scrum?</h3><p>The base level definition of scrum is very similar to Kanban. Scrum, in its simplest form, is a way to manage work, but in a time boxed manner. The time boxes are most commonly referred to as sprints.</p><p>Typically, sprints are two weeks long, but can be up to a month long. Each day, there’s a daily scrum that’s also sometimes referred to as standup. This daily meeting lasts no longer than 15 minutes and is a time to check-in on sprint progress. Each standup answers three questions:</p><ol><li>What did you do yesterday?</li><li>What are you working on today?</li><li>Do you have anything impeding your progress?</li></ol><p>This agile framework is used so that the product team (a.k.a. scrum team) can work as a group to meet a goal that’s valuable to the business. The framework is also widely used and accepted in product development because rather than planning out all requirements upfront, they are created along the way. This allows for shifts to happen much more easily and quickly, giving the team a chance to adapt to new requirements, changes in target and new technology.</p><p>Additionally, this particular framework allows for the measurement of velocity, which is the average amount of <a href="https://www.mountaingoatsoftware.com/blog/what-are-story-points">story points</a> a product team can accomplish within any given sprint. This allows for accurate projections to be made regarding releases.</p><p>Scrum has a lot more process behind it than Kanban does that we could write a whole article on, but we’ll just focus on the base level definition so that we can continue to compare Kanban vs Scrum.</p><h3>Pros &amp; Cons of Kanban and Scrum</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*FHm08_Uka19fg93h.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*sM55bpZnh2H32uGd.png" /></figure><h3>Middle Ground Options</h3><p>Scrum and Kanban are both viable and successful frameworks to use in product development. However, you should never be afraid to go beyond what is outlined as ‘standard.’ This is why we call them frameworks, because they are inherently flexible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2Ww8TpA9OlbTa-qM.png" /></figure><p>The beauty of Agile is that it was created to serve the individual team, and it’s not necessarily seen as ‘one size fits all’ when it comes to the framework used as an implementation method. Rarely will you come across a business or product that has been developed within a single silo of Scrum or Kanban — it’s just not all that common today.</p><p>It’s important to use a framework that works best for your team and your product goals. You may find that as you begin a creating product, you start with the goal of implementing via one framework, but utilizing components of other frameworks along the way.</p><p>For example: If you first decide to approach a product with the Kanban method, but would also like to implement a daily standup (or “Scrum” meetings) to ensure alignment throughout the team, you should feel confident in this decision.</p><p>There are documented approaches for overlaps within Scrum and Kanban (such as <a href="https://leankit.com/learn/agile/what-is-scrumban/">Scrumban</a> and <a href="https://www.atlassian.com/agile/kanban/kanplan">Kanplan</a>), but ensure that whatever method you choose to take, you don’t limit yourself or your team, just for the sake of following structure.</p><h3>What does Crema use and why?</h3><p>Crema uses all of these frameworks! We more commonly use the Scrum framework on our heavy product development work, but use Kanban more commonly with our design and <a href="https://www.crema.us/primer/prototypes">prototyping</a> engagements. Sometimes, we even use the middle ground options listed above. Frankly, we use whatever framework or combination of frameworks that make the most sense for the engagement. Our <a href="https://www.crema.us/product-management">Product Management</a> team analyzes each and every engagement that comes through our doors to determine the best method to produce the greatest results.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*EZxNIRMn2HohBIwM.JPG" /></figure><p>We tend to use the Scrum framework most heavily for our product development work, because it allows us to plan out work more effectively and deliver quicker results. Scrum also allows us to pivot if, or when, necessary, so that our clients still get something at the end of the engagement. While it may not be what they thought they were going to get at the beginning of the engagements, it better aligns with their business needs.</p><p>One of the main reasons Scrum allows us to plan work out more effectively is that our engagements are centered around a product team for a duration anywhere from three months to over a year. Since the teams remain largely the same throughout those engagements, it allows us to calculate a team velocity within the first two or three sprints. That velocity metric is a way for us to measure how much work we can get done within any given sprint, using story points, and then allows us to plan out the remaining work and estimate how long it will take to complete.</p><p>With all of this said, It’s important to call out that each of our product teams can run a little differently at times — depending on the need of the client, product, and individuals working towards the solution. Each time that you embark on the journey of building out a new product, it’s really important to understand that flexibility is key to not only the success of the overall solution being built, but also for the individual team members working towards their common goal. We love to use Scrum, and we love to use Kanban, but we are never afraid to flex in different areas (regardless of the core method that we’ve chosen) to allow for the team to grow, and deliver the very best possible product.</p><p>‍</p><h3>What tools do we like the most for each and why?</h3><h3><a href="https://asana.com/guide/videos/customer-webinars/clients/crema">Asana</a></h3><ul><li>Asana doesn’t really have a good way to use it for Scrum, but, it does work GREAT for Kanban style projects. As a product agency, we’ve used Asana for years and only recently had to begin to transition projects out that are prescribed a more Scrum style framework. You can learn more about how we use Asana in this <a href="https://www.crema.us/blog/tips-to-manage-your-team-with-asana">blog post</a>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fOrchF_3OUcLFYH3.png" /></figure><h3><a href="https://www.atlassian.com/software/jira">Jira</a></h3><ul><li>Jira is king for both Scrum and Kanban projects (and even projects beyond that). They’re the leading product development software used throughout the globe and there’s a reason for that. It’s incredibly robust and can handle pretty much any type of project you throw at it. That robustness does come at a cost though. Jira can be a lot to manage for newbies, but they’re doing a lot to fix that, including releasing an entirely new UI. I think we’ll see great things to come from Jira in the coming months and years.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5gzxYR-2F14bUso6Oer9tQ.png" /></figure><h3><a href="https://www.crema.us/primer/ora">Ora</a></h3><ul><li>Ora is a new player in the realm of digital product management, but they’ve really impressed us with their flexibility in nature. By default, Ora is set to manage projects within Kanban boards. However, their suite of options and features allow for teams with different preferences or goals to run their projects without restriction or prescription.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*edu2RYPV1vAn6ZaN.png" /></figure><h3>Summary</h3><p>We hope you enjoyed this article about Kanban vs Scrum and hopefully come away with some clarity around the topic. If there’s one thing to take away, it would be that flexibility is key. Do what you need to do for your team to produce the best results and you’ll be set!</p><p><em>Originally published at </em><a href="https://www.crema.us/blog/whats-the-difference-between-kanban-and-scrum"><em>www.crema.us</em></a><em>.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F3eee85%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2F3eee85&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/649b83359ed6c72f505d9bd1d5e9ed30/href">https://medium.com/media/649b83359ed6c72f505d9bd1d5e9ed30/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=647dec826a20" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ideas-by-crema/whats-the-difference-between-kanban-and-scrum-647dec826a20">What’s the Difference Between Kanban and Scrum?</a> was originally published in <a href="https://medium.com/ideas-by-crema">Ideas by Crema</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Perspective Matters]]></title>
            <link>https://tucker-sp.medium.com/why-perspective-matters-b2c7cdde09c0?source=rss-1e4060f40b18------2</link>
            <guid isPermaLink="false">https://medium.com/p/b2c7cdde09c0</guid>
            <category><![CDATA[self-awareness]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[relationships]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Tucker Sauer-Pivonka]]></dc:creator>
            <pubDate>Tue, 06 Feb 2018 20:44:09 GMT</pubDate>
            <atom:updated>2018-02-07T01:47:17.253Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NxsfFVSwE7szf3p4Ln2-hA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/Mg4TZbhjJ3M?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Sam Loyd</a> on <a href="https://unsplash.com/collections/1704057/my-first-collection/f3d6f8b9e5784ec01970dc11e4ef0ad3?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h4>Perspective Defined</h4><p><em>A particular attitude toward or way of regarding something; a point of view.</em></p><h3>Point of view</h3><p>Everyone in this world has their own life experiences; their worldview. This shapes who we are as a humans, whether that be good or bad. With that point of view, comes great responsibility. It’s easy to forget that everyone in this world has a different point of view than yourself. People tend to think that their beliefs are the only possible truth, and that everything or everyone else is wrong.</p><p>There’s no doubt that we’ve all been guilty of looking at a situation, or at life in general, solely through our lens. Through that, we tend to make our decisions, react, work, and so on. Only looking through this little lens of yours often leads to many undesirable traits such as a lack of empathy, misinterpretation, over-reactions, poor listening skills, poor decision making and so on.</p><h3>Why does this all matter?</h3><p>Well, without perspective, we are stuck in our own worlds, our own minds, our own way of doing things. The longer we go without gaining perspective, the more stuck in our ways we become and the harder it is to pull away from that.</p><p>A great example of this is the polarization we have been experiencing in U.S. politics. People on both sides of the aisle are often not willing to listen to the perspective of those on the opposite side of their own. Yes, there are exceptions, such as extremism, but one may argue that extremism was brought on by not attempting to view the perspective of the opposite side. In an ideal world, we need both sides (or many sides) providing their point-of-view to reveal solutions that offer the most significant benefit to all.</p><h3>At the core of perspective is…empathy</h3><p>As humans, we need to be empathetic to survive as a species. One can not be empathetic by lacking perspective. They come hand-in-hand. One must use perspective to understand what the other values. Once you understand those values, it begins to shift how you interact so that your interactions are meaningful. Generally speaking, this also makes people feel heard; and feeling heard makes people feel valued. Once you cross that barrier, either in your personal or professional world, you can begin finding genuinely creative solutions to all problems that come your way.</p><h3>What next?</h3><p>How does one gain perspective? Well, it’s a never-ending process, at least for me. It’s continually reminding yourself that there are multiple viewpoints for any one situation. Reminding myself of this is something I struggle with frequently; However, I’m getting better at identifying when I’m coming to a situation with my rose colored glasses on.</p><p>Now, I’m no authority on this subject matter, but I have found the following to be extremely beneficial to gaining perspective throughout my life thus far.</p><h4><strong>1. Read…a lot.</strong></h4><p>While I do think it’s important to be reading a book at any given time, I don’t mean read books exclusively. Read the news (even when it sucks), read articles that interest you and some that have views with which you may disagree, read Wikipedia articles about random subjects you come across…you get the drift.</p><h4>2. <strong>Listen.</strong></h4><p>Intently listening to someone while they’re speaking to you is challenging, because we typically try to think of what we’re going to say next. We naturally want to fill pauses in a conversation with words. Practicing your active listening skills will not only improve your perspective but your relationships overall, because you are processing what the person is speaking about, rather than thinking of what you have to say next. Fun side note — this also makes it easier to notice when people are full of shit (I’m definitely guilty of it).</p><h4>3. Get your ego in check.</h4><p>Last, but definitely not least, get your ego in check.<strong> </strong>It sucks to be wrong. That’s why most humans are generally defensive about their opinions, so much so, they begin to believe their views are facts. Often, this means that you may dismiss someone else’s perspective as less valid than your own. While someone can lack the amount of perspective you may have, that doesn’t mean it’s any less important than yours. If anything, by understanding that person’s perspective (or lack thereof), it will give you an excellent opportunity to educate them on why you have the perspective you do; and by proxy, may even allow their perspective to grow.</p><p>Did you enjoy this article? Give it some claps! <br>Have something to say (good or bad)? Comment below!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b2c7cdde09c0" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>