<?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 João Esteves on Medium]]></title>
        <description><![CDATA[Stories by João Esteves on Medium]]></description>
        <link>https://medium.com/@j-esteves?source=rss-2f055b2b65e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*qh_GA5kX9HAk_NtcI4nMAw.jpeg</url>
            <title>Stories by João Esteves on Medium</title>
            <link>https://medium.com/@j-esteves?source=rss-2f055b2b65e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 06:02:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@j-esteves/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[Scaling up Engineering Teams]]></title>
            <link>https://j-esteves.medium.com/scaling-up-engineering-teams-41914ffc42e5?source=rss-2f055b2b65e------2</link>
            <guid isPermaLink="false">https://medium.com/p/41914ffc42e5</guid>
            <category><![CDATA[scaling-up]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[change-management]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[João Esteves]]></dc:creator>
            <pubDate>Wed, 28 Jul 2021 07:32:10 GMT</pubDate>
            <atom:updated>2021-07-28T07:32:10.497Z</atom:updated>
            <content:encoded><![CDATA[<p>The below are thoughts shared by a group of professional in the industry that are experience in scaling up organisations or that are going through the process at the moment. I found them quite interesting and sharing this with you.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nGqalu-so3xWrRqZiz0fqg.png" /></figure><p><strong>Maturity needs to go hand in hand with Hiring</strong></p><p>when companies are successful in a round of funding they sometimes are keen to grow the engineering headcount, hoping that it will help them build product faster. In reality, it often can block the shipping process.</p><p>When you scale from 5 to 20 people you can get away with inefficiencies in the processes. But when moving from 20–100 people those inefficiencies will bubble up very quickly. If you 10x in 1–2 years, you will need to prepare and give it a lot of thought.</p><p><strong>Change Management</strong></p><p>Change is difficult for people. If it’s not manage properly it will create problems that you may not anticipate. Make sure you employ a change programme, get you allies, your comms plan in place, etc.</p><p><strong>Before Growing the Organization ask yourself</strong></p><ol><li><strong>Why are you Growing?</strong> This is the first thing to be answered. Is this a permanent need, or is it a temporary project that only last a couple of years.</li><li><strong>What will this growth support? </strong>Are you scaling to support the growth of the products? Or are you scaling to resolve technical foundational items?</li><li><strong>Are your people processes mature enough to deal with this growth? </strong>It’s not enough to think about the recruitment pipeline. How will you be able to onboard people without causing impact to the current business activity?</li><li><strong>Optimize the Onboarding</strong> — Is the onboarding well documented and able to cope with 10x the level of people that normally join in a month? You can’t rely only on buddies and human connections to scale your onboarding — documentation is key so that individuals can self-learn and self-onboard. Otherwise you will end up with a slower organization than what you had before.</li><li><strong>Visualize your org in the future — </strong>It’s not enough to think about what the next quarter will look like. The effort of going from 10 to 20 people is far easier than what it takes to go from 20 to 100. You need to prepare well ahead of time so that the foundation work is in place even before recruitment is approved.</li><li><strong>What does your role look like in the future org</strong> — If you now lead 20 people, what will your role look like when there’s 100 people? What will the roles of the current 20 people look like when there’s 100 people in the org? What type of problems will I be dealing with in that future state?</li><li><strong>Manage the transition for the existing team </strong>-</li></ol><ul><li>Are people being promoted too fast without having enough experience ?-</li><li>Think of the engineers who were stellar ICs in the small org, they knew everything and contributed in every area. Now in the new scale they have to share their contributions with others and don’t get the same sense of success and recognition.</li><li>There will be people who don’t want to work in the organization with the larger numbers.</li><li>Retaining the existing teams is fundamental. You can’t lose people faster than the rate at which you can hire. The existing team members are the rock of this scale-up, they need to be supported through the process.</li></ul><ol><li><strong>Communicate, communicate, communicate</strong> — Teams and individuals need opportunities to uncover dependencies across teams. Promote opportunities for this to happen: eg. scrum of scrums, all-hands, small meetings, 1:1.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=41914ffc42e5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Prioritise Engineering Work When Everything Is Important]]></title>
            <link>https://j-esteves.medium.com/how-to-prioritise-engineering-work-when-everything-is-important-10f364144147?source=rss-2f055b2b65e------2</link>
            <guid isPermaLink="false">https://medium.com/p/10f364144147</guid>
            <dc:creator><![CDATA[João Esteves]]></dc:creator>
            <pubDate>Thu, 22 Jul 2021 12:07:46 GMT</pubDate>
            <atom:updated>2021-07-22T12:07:46.513Z</atom:updated>
            <content:encoded><![CDATA[<h3>Problem</h3><p>One of the biggest challenges that most managers face is prioritising the work that matters on a day-to-day basis. Most of them are used to prioritising work either within a sprint or using agile methodologies. Stepping up to be a director or a senior manager means that you might be getting an influx of strategic initiatives, especially if you are in an area that gets many requests from outside or within the organisation. Sometimes, it is hard to manage all those requests unless there is a process or framework to handle that.</p><p>From my experience, I worked with a data team in my organisation, which was pretty new and small. They had merely started by implementing a <em>datalake</em> to ingest information from all the systems of the organisation. Once all the teams of the company realised the value of it, suddenly we had almost 20 streams of incoming requests for further use cases. It did cause a lot of confusion in the team to cope with the demand that they had, and at the same time, they didn’t feel empowered to say no.</p><p>The biggest challenge was that the team did not know which requests were more critical or highly prioritised. Furthermore, who should guide them by saying that something was more important than the other? This led the team to feel that they did not grasp the prioritisation framework and what they were doing.</p><h3>Actions taken</h3><p>My first approach to the problem was asking the team a simple question: <em>where did all of the work come from?</em> Their reply to the question was that the work came from everywhere — all the departments.</p><p>Sometimes having to escalate those questions or queries to the senior management was not a great situation to be in. I worked on resolving the problem. Since I knew where all the problems of the work were coming from, I worked towards that. I communicated with every team or people necessary to come to an outcome. And, communicating effectively was the glue that helped us stick everything together.</p><p>Best of all, the team knew what needed to be done. The obstacle in the middle was that they lacked a method to measure which item was more important than the other. In companies that are exponentially growing every day, it could be seen that the importance of every task changes every week.</p><p>We formalised the notion of a request funnel (borrowing from the sales funnel concept), where the heap of requests would come in, and the system would ask them questions in a detailed form. Answering those questions helped the team get a clear idea of what to expect from the problems and finally prioritise them for that reason. It was actually funny because what sounds like common sense did hit us hard from multiple directions. However, when we are in medium sized companies and trying to scale, we had to use some framework, and in our case, this worked great.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7i9_o7mGbkfeoDg3" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*uNaja6bMPLJVo7aD" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*yySU4b03OnhGe6X5" /></figure><p>We used a weighted matrix for prioritisation to react to changes quickly. We had some dimensions where we saw something coming in, and we would immediately look at the pros and cons of implementing some changes. We started by attributing value to all the diminutive dimensions, and in the end, they would get a score that helped them prioritise efficiently. If we did this for every large request that came in, they could compare those requests and prioritise accordingly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KmC3YpAHRhBCTXuBplAz7Q.png" /></figure><p>That, in turn, helped them to go back to the stakeholders and explain the roadmap. It was a concrete way of justifying the order of things they were going to do and why they would do it in a certain way. Finally, it became our process to explain ourselves better. Since we created a priority funnel, they now knew better as to what was more significant and beneficial for the business.</p><p>Many companies do QBRs and have them ingrained in their processes, which is undoubtedly a great idea to stay in tune with everything. Nonetheless, it is important to revise priorities proactively. Although it depends on the size of the company, how fast it is growing, and how extensive the array of stakeholders need to be informed, these are some aspects to not fail out on.</p><h3>Lessons learned</h3><ul><li>Product managers need appropriate tooling to manage requests, in the same way that teams use jira for managing their software delivery lifecycle. Slack or other private messaging channels should be avoided in this case, while emails can be a more appropriate trigger for a conversation. However, having a tool to capture such requests formally is actionable.</li><li>If problems come in from multiple sides, have the right metadata for the submitters to record them. Simple details like the urgency, who had requested it, and who it would impact from it can help in the prioritisation matrix.</li><li>Try to understand the problem that the business needs to solve, rather than having people describe to you a solution. Most people might think that it can be solved by giving the engineering team a solution, but they might not see the complete insights of how it can be done in reality. It just goes by the saying, “if I had asked people what they wanted, they would have said faster horses” — by Henry Ford.</li><li>Assign at least one product owner persona to manage each product backlog because the concept of ownership in an area and someone taking care of project intakes and strategic business needs is very hard. Instead of having one product strategist doing it for multiple areas, it makes more sense to have different people with adequate cognitive load to be accountable for.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=10f364144147" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[As I prepare to move into a different role in a different company it’s a perfect time to reflect…]]></title>
            <link>https://medium.com/take-the-lead/as-i-prepare-to-move-into-a-different-role-in-a-different-company-its-a-perfect-time-to-reflect-a490a796af8f?source=rss-2f055b2b65e------2</link>
            <guid isPermaLink="false">https://medium.com/p/a490a796af8f</guid>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[career-change]]></category>
            <category><![CDATA[retrospectives]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[careers]]></category>
            <dc:creator><![CDATA[João Esteves]]></dc:creator>
            <pubDate>Mon, 25 Jan 2021 16:20:17 GMT</pubDate>
            <atom:updated>2021-01-25T16:20:17.269Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yUzOtiTQjPAo8CwI45F8xw.jpeg" /></figure><p>As I prepare to move into a different role in a different company it’s a perfect time to reflect on the last 4 years of my career. In this article I’ll focus on what I learned, on what I regret, and on what I expect for the future.</p><p><strong>Top 4 Learnings for the last 4 years ?</strong></p><ul><li>listen more</li><li>Be kind and empathise</li><li>People are more important than work</li><li>Customer Outcomes are better than Project outputs</li></ul><h3>Listen More</h3><p>It’s easy to listen to the loud noises and the loud people. But it’s easy to discard the messages that are subtle, low volume and low frequency. I learned to tune in on those signs, and the people that don’t shout louder than all others. There’s an expectation that, as managers, we are paying attention to those signs and acting on them.</p><h3>Be kind</h3><p>I didn’t learn how to be kind, but I mindfully practiced empathy every day. Regardless of stress, or deadlines, or any of the other goals that we have to meet all the time. I am quite proud when people in my team feel safe to ask for time off, to go off sick, or to just say that they can’t be 100% focused on their job because of personal reasons. That is a trust foundation that will catapult a team into greatness.</p><h3>People are more important than work</h3><p>Shouldn’t have to be said. Surprisingly, I often still find myself explaining it to others. Your team’s wellbeing is more important than their current list of tasks. It’s fundamental as a manager you communicate this often. If you’re not well, your work will not be that good, and that cascades all the way down to the customers’ experience. And that’s where you need to focus, because that’s the ultimate goal and the one that makes your company profitable.</p><h3>Customer outcomes are better that project outputs</h3><p>It’s easy for engineering groups to get their mindset stuck on project outputs. But the reality is that your team’s goal isn’t to deliver a software artifact, or a new UI, or a set of webservices, or a report. Your team’s goal is to make sure that customer’s processes, lives, business milestones and goals, are achieved with higher quality, better user experience, less user effort and/or any improvement in the KPIs that are relevant.</p><p><strong>Top 4 things I would do differently</strong></p><ul><li>Defend the Vision and Mission more often.</li><li>Do less managing of outputs, and more leadership of people</li><li>Focus the product direction on customer outcomes, not on sales.</li><li>Delegate more</li></ul><h3>Defend the Vision and Mission more often</h3><p>Firstly you should defend the need to have a Vision/Mission/Purpose well engrained in the team’s day-to-day. I wrote about it here.</p><p>Secondly, you need to keep fighting for the life of that Vision — it’s not enough to talk about it once a year. You need to care for it like if it was a goldfish — with little bits of care every day, and once in a while “you change the water”. I wish I had done more of the latter. Software release rush, can stand in the way of assessments of higher order unless you purposely schedule time for these activities.</p><h3>Do less managing of outputs, and more leadership of people</h3><p>In my previous role, the team’s autonomy and mastery allowed me to delegate a great deal of operational and day-to-day activities. And that was great. It gave me time to get involved in a series of company wide initiatives and to volunteer to work on improvements that would benefit the engineering group rather than just my teams.</p><p>On the other hand, I should have redirected some of that spare time on excelling as the team’s leader. A balance was required, and I learned that it was balancing in a direction that I didn’t intend to.</p><p><strong>Top 3 wishes for the immediate future and my new role</strong></p><ul><li>Feel that my contribution has a meaning, that it’s fun, and that I’m learning.</li><li>Make sure that everyone my organisation feels the same</li><li>Build some really amazing products</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a490a796af8f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/take-the-lead/as-i-prepare-to-move-into-a-different-role-in-a-different-company-its-a-perfect-time-to-reflect-a490a796af8f">As I prepare to move into a different role in a different company it’s a perfect time to reflect…</a> was originally published in <a href="https://medium.com/take-the-lead">Take the lead</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Wellbeing in Winter Months]]></title>
            <link>https://medium.com/take-the-lead/wellbeing-in-winter-months-90a4197d0ff5?source=rss-2f055b2b65e------2</link>
            <guid isPermaLink="false">https://medium.com/p/90a4197d0ff5</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[zoom]]></category>
            <category><![CDATA[wellbeing]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[João Esteves]]></dc:creator>
            <pubDate>Tue, 10 Nov 2020 17:39:35 GMT</pubDate>
            <atom:updated>2020-11-10T17:44:38.173Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GebVZg4khKr6_zOrAuCRqw.png" /></figure><p>Recently I started thinking about the challenges of working remotely during the winter months.</p><p>I live in Ireland. It’s an amazing country and a beautiful island. The raw landscape beauty also comes with a good side portion of weather and dark winters. For someone like me, who grew up under the sun, this has a strong mental impact. It’s not uncommon to feel frustrated, lonely or eager for holidays throughout the winter. For so many people, this can easily lead to depression.</p><p>With that in mind it’s important to approach 2020’s winter season with a clear plan. This is a plan to emerge back in 2021 with a healthy mind, and with a sense of social belonging.</p><p>In my organization, we facilitated a session to uncover the estimated impact of remote work during the winter. Let’s look at what the engineering teams are saying.</p><h3>Major impacts to Wellbeing</h3><ul><li><strong>Long zoom days </strong>— some days can feel like they were filled with zoom meetings. In some instances they take over lunch time. Overall it leaves little time for breaks during the day.</li><li><strong>Screen time</strong> — with remote workers, the computer screen is the window to the world. Added to that, with social restrictions, it’s not uncommon that all social interaction is also done via a screen. And this adds to the mental fatigue, and therefore we are continuously tiring our brain with screen based activity.</li><li><strong>Working alone for long periods of time</strong> — despite having plenty of team meetings during the week, many of us still feel lonely. Consider a young engineer who works from a bedroom, or is sharing accommodation with others — working from a small area can look, and feel, a lot like prison.</li><li><strong>Flexibility</strong> — working for a company that strongly encourages schedule flexibility is a major benefit. It impacts workers in the sense that they can include their personal lifestyle in the daily agenda — for example taking 2 hours at lunch time to go for a run and enjoy daylight.</li><li><strong>Paired Work</strong> — working 1:1 with someone else, as for example coding, or white-boarding solution. This is the closest we can get to working close to someone and eliminating the feeling of being alone at work.</li><li><strong>Exercise and Sleep</strong> — this came up as a really strong point that impacts wellbeing.</li></ul><p>Post this, we inquired about what our company is doing that really helps control negative impact:</p><ul><li><strong>Working from Home Stipend </strong>— our company awarded everyone with 2 extra weeks of pay, an additional 500$ for equipping our home offices, and fitness activity costs reimbursement.</li><li><strong>Flexibility </strong>— once again, mentioned as something that is really holding things together at home.</li><li><strong>Support from Management</strong> — To have transparency of that is expected during these months and knowing when we would have to go back to the office. It was also important to note that mental health related employee programs were also seen as welcomed.</li></ul><h3>So what are individuals doing to look after themselves?</h3><p>This was the surprising bit. We filled a whole whiteboard with post-its. Everyone had an idea already of what’s been important to do so that they can look after their mind and body. Some examples:</p><ul><li>Exercise — yoga, running, cycling, sea swimming, walking, tennis…</li><li>Baking, cooking, eating, enjoying a glass of wine</li><li>Reading, listening to music, playing music</li><li>Family time, meeting friends</li><li>Video games, painting</li><li>Stay away from screens, limit access to news</li><li>Having some me-time, meditation</li></ul><p>So in general, there’s already a good amount of personal effort to counteract on the impacts that remote working can have on mental wellbeing. This can mean that so much more needs to be done to actually mitigate further problems.</p><h3>What can we do to make it better?</h3><p>The following are some actions that will lead us into Q4 and 2021 Q1:</p><ul><li>Engage with HR partners to reiterate what’s available to employees in terms of getting more leave, or how to move some excess of unused leave to the following year.</li><li>Create and communicate a <em>Zoom Health &amp; Safety plan</em></li><li>Hold a townhall and discuss ideas to reduce screen time.</li><li>Create addressable OKRs in the following quarter:</li></ul><ol><li>reduce zoom meetings by 10%</li><li>replace 30% of zoom based 1:1s by a phone call</li><li>100% of teams reassess working agreements</li><li>100% of teams have NO MEETINGS on Wednesdays mornings.</li></ol><ul><li>Re-communicate what employee programs are offering to individuals</li><li>In addition to already existent team fun activities, add organization wide activities to promote networking beyond your close work circle as well as allowing for breaks from development work.</li></ul><p>To measure the success of these we rely on team survey metrics. These quarterly surveys measure the team’s sentiment on motivation, belonging and general wellbeing. This is something that I’ll be paying close attention in the months ahead.</p><p>Personally speaking, demonstrating empathy and showing yourself as a relaxed and happy leader will go a long way towards generating a sense of confidence in those that work close to you. More than ever, we have to do well by the people that work with us, by being a friend and a trusted leader.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=90a4197d0ff5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/take-the-lead/wellbeing-in-winter-months-90a4197d0ff5">Wellbeing in Winter Months</a> was originally published in <a href="https://medium.com/take-the-lead">Take the lead</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Engineering Teams Thrive on Creativity and Innovation. Here’s How We Inspire Both at Workday]]></title>
            <link>https://medium.com/take-the-lead/engineering-teams-thrive-on-creativity-and-innovation-heres-how-we-inspire-both-at-workday-b7282599a58d?source=rss-2f055b2b65e------2</link>
            <guid isPermaLink="false">https://medium.com/p/b7282599a58d</guid>
            <category><![CDATA[leadrship]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[creativity]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[innovation]]></category>
            <dc:creator><![CDATA[João Esteves]]></dc:creator>
            <pubDate>Tue, 10 Nov 2020 16:31:03 GMT</pubDate>
            <atom:updated>2020-11-10T16:31:03.949Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8HnxT4HBHpKaZMM4N4HiuQ.png" /></figure><p>I’ve been thinking about why I joined Workday in 2017 and what keeps me here. One thing that stands out is Workday’s approach to <em>creativity</em> and <em>innovation</em> and what that means for my team, me, and developing products.</p><p>When I joined Workday, these are the three things that stood out:</p><ol><li>Workday’s leadership and growth in Europe: As a quickly growing global company with some of the industry’s most respected leaders, Workday offered me career stability, the opportunity to work with inspirational people, and long-term growth.</li><li>To work as a people-focused engineer leader: I was a technical lead before joining Workday, and wanted to grow my skills managing a team and helping others reach their full potential. I knew Workday’s employee-first culture would enable me to do both.</li><li>To help build a meaningful product: I wanted to work on a product that has a positive real-world impact. Workday serves approx. 7,700 customers globally and more than 45 million users worldwide that depend on our products to do their jobs. Additionally, Workday’s forward-thinking approach to work meant I’d be able to act quickly to help bring new ideas to life.</li></ol><p>As an engineering leader, I’m adding “inspires creativity and innovation” to my list of what makes a company great to work for. I’m proud to share my experience with this at Workday.,</p><h3>Innovation and Creativity at Workday</h3><p>Innovation is one of Workday’s <a href="https://www.workday.com/en-us/company/careers/culture.html">six core values</a>. But more than that, it’s a company mindset. At Workday, I’ve learned that to get innovation right, you need to invest in creativity, which helps you discover new and better ways to solve problems — whether it’s solving them faster, more efficiently, to be more future-proof, with new tools and technologies, and more.</p><p>Creativity is a precursor to innovation, but you can’t force it. Our engineering team invests in things like hackathons, innovation weeks, and design-thinking practices. Additionally — and where Workday really shines — we inspire creativity through curiosity by supporting employees to explore work and non-work related interests. More on that below.</p><p>Workmates (what we call Workday employees) are encouraged to flex their individuality, and enjoy their time at work through things like work clubs and taking breaks to have fun and focus on their wellbeing.</p><h3>Encouraging Creative Flow at Work</h3><p>On Workday’s Engineering team, we know how to solve most technical problems. But when our Workmates can get into a flow, they are faster, better at problem-solving, and bring more ideas to the table. That’s why I joined a rock band and started a club at work: to foster my own creativity and encourage flow in others.</p><h3>Having Fun with Workmates</h3><p>Music is one of my favorite outlets, but I stopped jamming with other people when the pandemic started.</p><p>Workday has a huge variety of work clubs, including a Dublin, Ireland rock band that I had known of for a while, but I have a young family to support and could never find the time to play with them. When we all went remote, I decided it was time to join.</p><p>We’ve remotely recorded a few songs since, and not only is it a ton of fun, but I think the results are pretty cool.</p><p>Having fun and sharing my interests with my Workmates provides me with a mental release throughout the work day. After a break, I feel refreshed, refocused, and ready to tackle engineering problems with a new mindset. Workday’s <a href="https://globalimpact.workday.com/a-better-place-to-work/wellbeing.php">approach</a> to supporting employees’ wellbeing makes these breaks possible.</p><h3>Stepping Outside Your Day-to-Day</h3><p>Becoming more innovative at work can also be about pushing yourself to grow outside your comfort zone through creative forms like public speaking.</p><p>To encourage my team to grow in new ways, I organized an optional public speaking workshop last year. I was surprised when the invite started being shared outside of my direct team, and by the time the workshop took place, Workmates from across our organization attended. Because of the large interest, I started thinking about how creative communication benefits people at Workday, adds to our core value of Innovation, and sets people up for successful careers. And so, after the workshop, I decided to launch Workday’s Dublin Toastmasters club.</p><p>Here’s an example of one of our remote Toastmasters sessions:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*qPYycqKHj4q33S2g" /></figure><p>Workday’s Dublin Toastmasters club has been active for about a year, and it’s a fun, casual way for members to change their day-to-day pace at work. Whether it’s public speaking or something else, I want my team to take time to explore the things they’re curious about — not only because it makes for a happier team, but people often come back with new ideas and perspectives on the technical problems we’re solving at work.</p><h3>Final Thoughts</h3><p>Creativity and innovation are essential in technical teams, and I love being in a work environment that promotes a positive approach to both. Yes — being in a work band and a club lead are fun, but getting creative with teammates has an impact that Workday understands well:</p><ol><li>When employees are encouraged to show creativity, this has a positive impact on the team and individual satisfaction, how quickly goals are reached, and the frequency, impact, and innovation of ideas.</li><li>Being creative and enjoying time at work makes employees happier, more balanced, and fulfilled. Not only that, but happy employees = happy customers.</li></ol><p>Leaders should encourage their teams to explore curiosities, and employees should look for company cultures that provide the support and resources to do this. It’s an idea that will impact my career for years to come.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b7282599a58d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/take-the-lead/engineering-teams-thrive-on-creativity-and-innovation-heres-how-we-inspire-both-at-workday-b7282599a58d">Engineering Teams Thrive on Creativity and Innovation. Here’s How We Inspire Both at Workday</a> was originally published in <a href="https://medium.com/take-the-lead">Take the lead</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Here’s some feedback about feedback]]></title>
            <link>https://medium.com/take-the-lead/heres-some-feedback-about-feedback-1b7b74357aa0?source=rss-2f055b2b65e------2</link>
            <guid isPermaLink="false">https://medium.com/p/1b7b74357aa0</guid>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[management-and-leadership]]></category>
            <category><![CDATA[leadership-skills]]></category>
            <category><![CDATA[feedback]]></category>
            <category><![CDATA[coaching]]></category>
            <dc:creator><![CDATA[João Esteves]]></dc:creator>
            <pubDate>Mon, 20 Jan 2020 15:35:38 GMT</pubDate>
            <atom:updated>2020-01-20T15:35:38.158Z</atom:updated>
            <content:encoded><![CDATA[<p>In the past year, there were a couple of things I was working to be better at. I knew what my team thought wasn’t great about our environment, but it was hard for them to pinpoint what I could do to make it better. So my quest to diagnose problems starts</p><p>When I do 1:1 meetings there’s inevitably a space for “What’s one thing that I can do to make you enjoy your job even more?” About 50% of my team has a hard time providing constructive feedback or suggestions for improvement, but when asked anonymously, they think something can be done better.</p><p>It’s this communication problem that is often a cause for the lack of engagement in the software engineers. In fact, not only in this particular career. When I ask my family or peers about their work environment in different industries, the trend is pretty much the same. Constructive feedback is often seen as a negative and awkward situation.</p><p>So how can I fix this for my team?</p><p>The 3 questions I base my investigation are:</p><ol><li>Am I exhibiting the same behavior?</li><li>How can we build a trust foundation so that feedback can flow easily?</li><li>What mechanisms already exist for providing feedback?</li></ol><h4>Am I exhibiting the same behavior?</h4><blockquote>Feck! I am doing the exact same.</blockquote><p>It’s hard for me to tell my boss what he can do better. It feels weird to provide constructive feedback to the person that will eventually decide my promotion or salary changes. Unconsciously, I was trying to just do <em>everything right</em>, and somehow negative feedback is classified by my brain as confrontation.</p><p>But here’s the thing, I want my team to give me the nasty feedback. I can take it (in fact, I need it<strong>)</strong>. I need to learn what I can do better, and what I suck at. And so does my manager. So the first step is to change my mind, and to be proactive in providing my manager regular feedback during our 1:1s.</p><h3>How can we build a trust foundation to enable more feedback ?</h3><p>This takes a bit of time but it’s the best investment: trust has to be earned.</p><p><strong>Show that you care about the people you manage, at a personal level.</strong></p><p>To care about someone is to listen attentively to what they say to you. It is to care about what makes their brains tick, and what their dreams and aspirations are.</p><p>In some 1:1 meetings I tried to tap into the dreams and aspirations of the members of my team. When I started asking people what their dreams were, I wasn’t expecting to just hear about “becoming a CTO, or an architect”. I was also really looking forward to hear something like “I want to create my own business” or “I want to be a mountain guide in the Alps”. Even though the company I work for might not provide roles directly in line with those dreams, as a manager it’s possible for me to provide experiences that would help my team get closer to their big goals. Experiences such as opportunities for public speaking, organizing events, or project management are invaluable for any other career.</p><p>To care about someone is to understand the difficulties in their job, but in their life also. I don’t mean to breach any privacy limits, but to empathize when private situations are shared. I have a duty of care to the people I work with, and as a manager I can make sure that the work load, stretch assignments or work flexibility are in line with those situations where you need to pay extra attention to your personal affairs.</p><h3>Feedback Delivery</h3><h4>1) Before delivering feedback:</h4><ul><li>Ask permission to give feedback.</li><li>If it’s a hard conversation, tell the person the topic of the discussion ahead of time. This allows them to think about it and not be surprised.</li><li>If it’s something simple, you don’t need to book a room, sit down and be so formal. Pull them aside and in 2 minutes you can deliver your observations.</li><li>Think about what you are going to say, and make sure it’s objective, concise and concrete. This avoids going on a rant, and improvising, hence making you look unsure of the feedback you are giving.</li></ul><h4>2) What feedback frameworks can I use?</h4><p>This is the easy bit for someone with an engineer’s mindset. All I want is a framework, a set of rules or a guide to explore a difficult conversation. These tools are well described at the distance of a google search, but it’s only until you really push these techniques into your day-to-day brain that you start to really provide and receive quality feedback.</p><p>Should I assume that lots of people are aware of this? No.<strong> </strong>The other day, while preaching the benefits of structured feedback to a development team, one of the team members mentioned that it’s really hard to go over to someone and tell them something like “Listen mate, you have to start pulling your own weight and stop being so freaking complacent”. I know what you are thinking: why would you talk like that to a colleague? It’s basically an aggressive judgement.</p><p>To provide professional and cordial feedback, the most important mindset change is: <strong>Focus on the work produced by someone — rather than on the person that produced the work.</strong></p><p>These are 2 very well know approaches to structured feedback:</p><h4>SBI — Situation Behavior Impact</h4><p><strong>Situation</strong> — provide the context. You should mention the time, place and environment where the situation you are referring to occurred.</p><blockquote>Example: “Yesterday during the stand-up meeting when I was giving my updates…”</blockquote><p><strong>Behavior</strong> — detail the behavior that you are trying to address. The important aspect here is to be objective and use measures that you can compare to expectations — any ambiguity renders this feedback useless. Using words such as “good” or “bad” is ambiguous.</p><p>Use facts that you directly observed and never use observations made by others as this could be incorrect and affect your relationship with the person. Don’t make assumptions or derive conclusions as these can be incorrect.</p><p>Focus on the work done and not of the person. As an example: If something was said that offended you, focus on the message, not on the person saying it. Don’t make it personal.</p><blockquote>Example: “Yesterday during the stand-up meeting when I was giving my update you said that my work is irrelevant for today’s priorities”</blockquote><p><strong>Impact</strong> — Explain how that person’s actions has affected you or others.</p><blockquote>Example: “Yesterday during the stand-up meeting when I was giving my update you said that my work is irrelevant for today’s priorities, and that sort of statement made me feel humiliated.”</blockquote><p>Now that you have described the Situation, Behavior and Impact, the next steps are to allow some time to absorb the information and follow with Expectations Vs Reality.</p><p><strong>Expectation </strong>— Describe what you expect in that particular situation. What should’ve been a great alternative situation?</p><blockquote>Example: “I expect my colleagues to be positive and supportive of all team members. If I am not working on the right priorities, I expect to be aware of that and not be told in public that I am not doing the right thing. And the reality is ….”</blockquote><p><strong>Reality </strong>— Compare your expecation with the reality and explain how what happened isn’t matching the expectation. The result of that comparation is either positive (when someone goes above and beyond) or negative (when someone behaved bellow expectations).</p><p><strong>Actions </strong>— Reach an agreement first of all, or give it some time to process the information and come back to discuss it further. This might look like a list of actions to remediate the negative situation, or to build on top of the positive situation. This might look like an agreement that moving forward the same situation will be different and not repeated. It’s important to agree.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dX9xMJ_JoUCKjBRFztHa3Q.jpeg" /></figure><h4>Radical Candor</h4><p>Kim Scott has brilliantly distilled her years of experience in a number of companies such as Google and Apple, into a set of concepts that helps create work environments where people love their work and the people they work with.</p><blockquote>Radical Candor™ is Caring Personally while Challenging Directly. At its core, Radical Candor is guidance and feedback that’s both kind and clear, specific and sincere. (in radicalcandor.com)</blockquote><p>The bellow diagram sums it up into the 4 areas that your behavior as a manager can fall into:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*14d4twbWY4uEScCbQj_9bw.png" /><figcaption>in Radical Candor (radicalcandor.com)</figcaption></figure><p><strong>Ruinous Empathy</strong> — this happens when you care a lot about someone, but you end up not telling them the hard-truths because you either want to spare their feelings or are afraid your relationship will suffer.</p><p><strong>Obnoxious Aggression</strong> — when you aren’t demonstrating any care or empathy with the person, but yet challenge directly. This can be perceived as aggressive and unkind.</p><p><strong>Manipulative Insincerity</strong> — a horrible type of feedback, when you don’t tell the truth and don’t care about the person. This is the sort of political backstabbing that you can experience in cutthroat environments.</p><p><strong>Radical Candor </strong>— when you care about the person, and you challenge directly.</p><blockquote>I would argue that criticizing your employees when they screw up is not just your job, it’s actually your moral obligation.</blockquote><p>It sounds simple but it’s actually hard to accomplish. You see, for this to work you need to have a good foundation of trust and respect for it to work. The employee needs to understand that you care, and you need to demonstrate often that you care. They need to know it, and they need to feel it.</p><p>If you give someone direct clear feedback when they screw up, but haven’t demonstrated care, then you just sound like an asshole.</p><p>Being an asshole is still better than not challenging your team. Make sure you do your job by telling people when they screw up. Failing to do so in a caring way is not helping them in their career.</p><h3>Summary</h3><p>Feedback is how you know if you are doing well or not. You have an obligation to your work environment to give feedback in a timely and professional manner. Being objective and not delivering personal criticism is the key to growing successful teams and individual careers. To do so you can employ a structure such as SBI to guide your conversation, and Radical Candor to set the relationship stage. When you don’t provide negative feedback you are not doing a service to the person. In fact you are perpetuating a behavior that is not expected. When you don’t provide positive feedback you are missing out on recognition, and therefore not rewarding the good behaviors. Give quality feedback often, people will thank you and everyone benefits.</p><h4>Further reading</h4><ul><li><a href="https://www.radicalcandor.com/our-approach/">Radical Candor | Our Simple Approach To Feedback</a></li><li><a href="https://www.radicalcandor.com/direct-reports-radical-candor-feedback/">Direct Reports And Radical Candor: 5 Tips For Giving Guidance And Feedback</a></li><li><a href="https://simpleprogrammer.com/developers-personal-feedback/">How Developers Can Benefit From Personal Feedback - Simple Programmer</a></li></ul><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F-oRKr5xA9N0%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D-oRKr5xA9N0&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F-oRKr5xA9N0%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/3e1099a40028ad6af17ba7855dc5f19a/href">https://medium.com/media/3e1099a40028ad6af17ba7855dc5f19a/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1b7b74357aa0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/take-the-lead/heres-some-feedback-about-feedback-1b7b74357aa0">Here’s some feedback about feedback</a> was originally published in <a href="https://medium.com/take-the-lead">Take the lead</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Does your team have a Vision and Purpose ?]]></title>
            <link>https://medium.com/take-the-lead/does-your-team-have-a-vision-and-purpose-1f9f489b3ae2?source=rss-2f055b2b65e------2</link>
            <guid isPermaLink="false">https://medium.com/p/1f9f489b3ae2</guid>
            <category><![CDATA[alignment]]></category>
            <category><![CDATA[mission]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[vision]]></category>
            <category><![CDATA[purpose]]></category>
            <dc:creator><![CDATA[João Esteves]]></dc:creator>
            <pubDate>Tue, 07 Jan 2020 11:25:11 GMT</pubDate>
            <atom:updated>2020-01-07T12:40:08.181Z</atom:updated>
            <content:encoded><![CDATA[<h3>Does your team have a Vision and Purpose ?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*x1Vz8qmoUXbQzNfD" /><figcaption>Photo by <a href="https://unsplash.com/@goian?utm_source=medium&amp;utm_medium=referral">Ian Schneider</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>A few months ago, the development teams in my organization were challenged to define and publish a “Team Vision and Purpose” canvas in their areas. The output of this exercise is usually a large poster that outlines the team’s vision, purpose, goals, agreements, and any other information the team believes is core to their effectiveness, and therefore should be made public.</p><p>Sounds easy right? In theory, for an existing successful team, we should know what we’re doing, we know what we will be doing in the next few product releases, and kinda know what the product vision is. Easy, right? Not so much as I discovered.</p><p>This turned out to be a little bit more challenging, so here’s what I learned.</p><h3><strong>Problem 1 — Death by concepts</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*w2kDn3w8udfGCxzC" /><figcaption>Photo by <a href="https://unsplash.com/@waldemarbrandt67w?utm_source=medium&amp;utm_medium=referral">Waldemar Brandt</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>The exercise kicks off by introducing what the end result is and the concepts that we’ll be discussing.</p><p>Suddenly we’re hit with words like <em>Mission, purpose, goals, OKRs, product vision, team vision, values, agreements, attitudes, alliances, strategies</em>… and we feel like this is <strong>death by concepts</strong>.</p><p>Development teams tend to be more comfortable with tangible outputs. So the first iteration of this exercise crashes here, as teams get overwhelmed by the tsunami of abstract concepts.</p><p>As a facilitator it is crucial to have clear definitions and examples of what each concept means:</p><p><strong>Vision</strong> — this is where the team (for team vision) or product (for product vision) wants to look like. It is a description of the most desirable future state. You should be thinking big and aspirational when crafting this statement.</p><p><strong>Purpose or Mission</strong> — this is why the team was created and why the team exists. What are the reasons for keeping this team?</p><blockquote>An effective mission statement describes the firm’s fundamental, unique purpose … [it] indicates what the organization intends to accomplish, identifies the markets in which the firm intends to operate, and reflects the philosophical premises that are to guide actions. [1]</blockquote><p>Most companies make their Mission statement public, so these can serve as inspiration for your team. [3]</p><p>Mission and Purpose are two concepts often confused; I prefer to pair them up under one statement. For the remainder of this text I will refer this paired statement as <em>Purpose</em>.</p><p><strong>Values</strong> — principles considered of worth, which the team agrees to align to.</p><p><strong>Agreements</strong> — The rules of behavior that the team considers crucial to follow so that they can achieve their purpose and vision.</p><p><strong>Market Forces</strong> — this is often masked as product vision, but it should be more clearly defined. These are the facts about the environment where the company or team operates and/or competes. These are crucial to determine the future vision, and can change often. A product vision will in turn strongly consider these.</p><p><strong>Strategy</strong> — This is how we achieve the Vision is broad statements.</p><p><strong>Goals</strong> — these are things that must be achieved to fulfil the strategy.</p><p><strong>Action</strong> — Things that are done to accomplish goals.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/760/1*fkVMMI_5b-CskkgedPe4BQ.png" /></figure><p>Enough of definitions, let’s run the above through a fictional example:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6FnDe0VUkjK713vq" /><figcaption>Photo by <a href="https://unsplash.com/@billjelen?utm_source=medium&amp;utm_medium=referral">Bill Jelen</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><blockquote>AboveAndBeyond is a company that wants to put private customers in space at affordable prices and give them a memorable experience.</blockquote><p>Values — <strong>Achieve</strong> innovation towards efficient travel; <strong>Be</strong> profitable through large scale sales; <strong>Be</strong> a safe environment for employees and customers.</p><p>Core competencies — An experienced force of aerospace engineers, pilots, marketing teams and safety officers. Ability to deliver projects with strict safety guidelines and low costs.</p><p>Purpose — <strong>We believe</strong> that you don’t need to be a millionaire to be able to go to space.</p><p>Market forces — a market where there are companies that have years of experience and research, but focus only on the luxurious experience of traveling to space. There aren’t many companies doing this, therefore it’s not an accessible experience.</p><p>Vision — <strong>We will</strong> provide space travel as an affordable and unforgettable positive experience that most people can achieve in their lifetime.</p><p>Notice the use of certain terminology such as:</p><ul><li>“Be”, “Do”, “Make” for values;</li><li>“We believe” for purpose;</li><li>“We will” for vision.</li></ul><p>There are a number of attributes that help measure the quality of the Vision and Purpose statements.</p><p><strong>What are the desirable attributes of Vision?</strong></p><ul><li>Brevity</li><li>Clarity</li><li>Future Orientation</li><li>Stability</li><li>Challenge</li><li>Abstractness</li><li>Desirability or ability to inspire</li></ul><p><strong>What are the desirable attributes of Purpose?</strong></p><ul><li>‘reason for existence’</li><li>‘rallying cry’</li><li>‘identifies markets’</li><li>‘indicates what the organization intends to accomplish’</li><li>inspirational and easily memorized</li><li>12 words or less</li></ul><h3><strong>Problem 2 — Engineering teams prefer to prioritize delivering customer features over stopping and defining vision and purpose.</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*b42G4ELAqTeDpvc8" /><figcaption>Photo by <a href="https://unsplash.com/@dmey503?utm_source=medium&amp;utm_medium=referral">Dan Meyers</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><strong>Why should teams employ their efforts in creating statements that define the vision and purpose?</strong></p><p>A clear team vision is crucial to the success of a team because it defines what everyone should be aiming at; otherwise all the team members would be working on their own goals and agendas. With a clear vision, everyone works together towards a unique and well defined future state.</p><p>It also empowers teams to decide what is the correct thing to do. Knowing what your goal is will help decide what is the next feature, the next architecture priority, the next tech debt to fix.</p><p>At a business level it helps you creating a strategy and planning for the next move, the next product, the next iteration.</p><h4>Spending some time clarifying the benefits will be crucial to the engagement of everyone involved.</h4><p>If a team does not engage with this exercise, they will end up as a <em>building pipeline</em> that works on what someone else thinks is right. This will inevitably lead to further lack of engagement, employee retention problems, and often building something that does not scale, isn’t easy to maintain and is impossible to adapt to future use cases. This lack of focus and direction, besides being expensive, can kill a team, a product and even a company.</p><h3>Let’s get to work</h3><h4><strong>Before you start…</strong></h4><ul><li>Make sure the participants are not tight for time, are engaged with the activity and believe in the outcome.</li><li>Set a few hours aside for the first meeting or meetings. Plenty of breaks. Bring food and drinks.</li><li>Employ a structured approach and have a well defined agenda. eg. see Google’s Rework resources[2]</li><li>Have a facilitator keep structure and time discipline</li><li>Send pre-work and reading material. This will make participants think about the goal of the meeting.</li><li>Share the agenda, slides and all the info ahead of time. Some participants will want to visualize the session before it starts. It will help them engage better.</li></ul><h3><strong>Step 1) Craft the Vision and Purpose Statements</strong></h3><ol><li>Gather the appropriate <strong>participants</strong>. Make sure it’s a well represented group from your team. i.e. not just developers, or just managers, or just tech writers. — needs to represent all roles within the team.</li><li>Generate, debate and rank <strong>values</strong>. Select the top 5–8 Values.</li><li>Generate the <strong>purpose</strong> statement — <em>Why does the team exist? What do we believe in? What will we do every day to use our skills and uphold our values towards our Vision?</em></li><li>Generate the <strong>vision</strong> statement — <em>What will our team be like in 2–3 years? What do we want to be known for? In the future, we get publicly recognized — what did we do well?</em></li></ol><h3><strong>Step 2) Produce a canvas and publish it.</strong></h3><p>If you google <em>team canvas</em> or <em>team charter</em>, you will find lots of examples and inspiration such as the ones below. [5] One thing you will probably notice it that no one will be a 100% fit to your team or org. So the best thing to do is to pick out the concepts that are important to be visible to your teams, get a graphic designer, or just do it in any simple graphic design app (a ppt slide will do just fine). The important thing is that you have something that you can print in large scale and post on the office wall so that everyone knows what the team does, who, how and why.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*omSkE1nRZkUPFp73.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HWSAM7Bpv4HBzEkz.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*OpIU9VCX3VmFAbzY.png" /></figure><h3>Next Step after this?</h3><p>Now that you have shared Vision and Purpose you have the foundation for successful team. Congratulations!</p><p>The next step is to figure out the strategies, goals and actions that you must execute. I’ll save that for another post.</p><h3>Summary</h3><p>We need to treat Vision and Purpose with the same serious attitude that we treat the quality of our products, reliability of our software and the impact that our deliveries have on customers. We’ve seen above that there are frameworks to help you get started, but it’s also important to adapt them to the reality of your teams. There is no right approach, but there is a desirable outcome — <strong>a team that is aligned in the way that they work, of what they want to accomplish, and how they will get there</strong>.</p><h3>Useful Resources</h3><h4>[1] That vision thing, do we need it?</h4><p><a href="https://www.sciencedirect.com/science/article/abs/pii/S0024630198800046#!">Raynor, Michael E.</a>, Harvard Business School in Cambridge, Massachusetts USA</p><p><a href="https://www.sciencedirect.com/science/article/abs/pii/S0024630198800046">That vision thing: Do we need it?</a></p><h4>[2] Google’s manager’s guide to set and communicate a team vision</h4><p><a href="https://rework.withgoogle.com/guides/managers-set-and-communicate-a-team-vision/steps/introduction/">re:Work - Guide: Set and communicate a team vision</a></p><h4>[3] Mission statement Examples</h4><p><a href="https://www.missionstatements.com/">MissionStatements.com -The largest collection of mission statement samples</a></p><h4>[4] How to define purpose and vision</h4><p><a href="https://academy.nobl.io/how-to-define-your-purpose-vision-mission-values-and-key-measures/">How to Define Your Purpose, Vision, Mission, Values, and Key Measures</a></p><h4>[5] Canvas, Canvas, Canvas</h4><p>DesignABetterBusiness provides fantastic Canvas templates as well as the facilitation guides to work them out.</p><p><a href="https://www.designabetterbusiness.tools/tools">DesignABetterBusiness.tools | Tool Overview</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1f9f489b3ae2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/take-the-lead/does-your-team-have-a-vision-and-purpose-1f9f489b3ae2">Does your team have a Vision and Purpose ?</a> was originally published in <a href="https://medium.com/take-the-lead">Take the lead</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>