<?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 Nick Friebel on Medium]]></title>
        <description><![CDATA[Stories by Nick Friebel on Medium]]></description>
        <link>https://medium.com/@nicholas.friebel?source=rss-25eebc7a02a4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*PwG5AuQGtH7mA6O9BLXGxg.jpeg</url>
            <title>Stories by Nick Friebel on Medium</title>
            <link>https://medium.com/@nicholas.friebel?source=rss-25eebc7a02a4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 04:08:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nicholas.friebel/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[Service Blueprinting in EdTech (Clever’s Journey)]]></title>
            <link>https://medium.com/ux-of-edtech/service-blueprinting-in-edtech-clevers-journey-55904419ddce?source=rss-25eebc7a02a4------2</link>
            <guid isPermaLink="false">https://medium.com/p/55904419ddce</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[edtech]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[service-design]]></category>
            <dc:creator><![CDATA[Nick Friebel]]></dc:creator>
            <pubDate>Tue, 09 May 2023 16:15:58 GMT</pubDate>
            <atom:updated>2023-05-10T17:50:08.438Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Co-written by </em><a href="https://www.linkedin.com/in/snehavrao/"><strong><em>Sneha Rao</em></strong></a><em> and </em><a href="https://www.linkedin.com/in/nicholas-friebel/"><strong><em>Nick Friebel</em></strong></a>, <em>teachers turned designers who work at </em><a href="https://clever.com/"><strong><em>Clever</em></strong></a><em>, an EdTech company focused on unlocking digital learning for all students.</em></p><figure><img alt="Customers sitting at a restaurant table (frontstage), cooks in the kitchen (backstage), and the line of visibility between them." src="https://cdn-images-1.medium.com/max/1024/1*Mp20ueQjP2zOOODP2DLI9w.png" /><figcaption>Source: <a href="https://www.slideshare.net/KuldeepKulshreshtha/take-a-holistic-view-of-your-product-with-service-blueprints-at-uxsea-summit-2018">Benjamin Bowes</a></figcaption></figure><p>As product designers, we sometimes frame our customer experiences only within the products we create. However, understanding the customer journey beyond the product provides a much clearer picture of your organizations’ overall service, which can reveal critical insights and inform how you design the customer experience. To capture that complete customer journey, service blueprinting can help you map out the orchestration of people, touch points, processes, and technology both frontstage (what customers see) and backstage (what happens behind the scenes).</p><h3><strong>Why make a service blueprint?</strong></h3><p>The biggest benefits of a service blueprint are that you can use it to:</p><ol><li><strong>Gain alignment and a shared understanding of an end-to-end service experience. </strong>Service blueprints are particularly valuable when multiple teams need to come together to deliver on a vision for a service. This is also why when building your service blueprint, you should have representation from these different groups to help capture the whole picture.</li><li><strong>Visualize all the interactions, dependencies, and breakdowns of a service concept.</strong> A service blueprint will help you visually communicate all aspects of what can be an abstract concept, and makes it more tangible. This will ultimately make it easier to picture where and how existing and future ideas fit into a service and allow you to make more meaningful conversations with stakeholders or anyone outside of your immediate team.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fqig1X8vq16SDVs0O0lASA.png" /><figcaption>Clever App Store Home</figcaption></figure><h3><strong>Creating a service blueprint for the Clever App Store</strong></h3><p>At Clever we used service blueprints to map out the existing service and ideal, future service of how school administrators purchased educational technology through the Clever App Store. For a school administrator searching for a software solution, it was difficult to :</p><ul><li>browse or compare the different options on the market</li><li>see feedback from other educators who’ve used the product in the field</li><li>seamlessly roll out edtech solutions to the classroom</li></ul><p>As a result, the end to end purchasing process is time consuming, easy to mess up, and classrooms feel the impact. The long term goal of Clever’s App Store team was for Clever to address this problem and become the go-to place for school administrators to discover, evaluate, and purchase educational resources.</p><p>At the time, we were a new team who was brought together to define and execute on a visionary experience for school purchasing through Clever’s App Store but we all had different levels of knowledge regarding this problem space and what the existing service looked like. The blueprint of the existing service of school purchasing allowed us to identify all of our assumptions and knowledge gaps. This ultimately informed a research plan that we used to go learn about all the key players in school purchasing such as edtech coaches, assistant principals, schools principals, and financial assistants. We were then able to update the blueprint of the existing service model with validated pain points, which gave us a really clear birds-eye view of how school administrators purchased educational technology.</p><figure><img alt="A collection of sticky notes organized into a service blueprint showing what the school purchasing process looks like today." src="https://cdn-images-1.medium.com/max/1024/1*6ohggXYawJZBiAv-FDjd9Q.png" /><figcaption><em>The service blueprint of the existing school purchasing service</em></figcaption></figure><blockquote>We had a lot of great ideas about the service that we wanted to provide but it wasn’t until we mapped out a service blueprint for our vision that we started to explore business and operational viability.</blockquote><p>We were able to quickly see the operational issues that needed to be addressed in order to deliver the service. Questions started to surface around how were we going to process payments, how were we going to loop in the finance team, and how were we going to notify the application being sold.</p><blockquote>This is when we also discovered that we could have multiple service blueprints at different zoom levels.</blockquote><p>For example, school administrators had a few different payment method options from paying with credit card, PO, and check. Each type of payment method had its own sub-service. We were able to zoom out to cover a large amount of the experience regarding payment methods at a low level of detail AND zoom in to cover a smaller part of each payment method experience in more detail. Because of the scale of our service we needed multiple blueprints at different levels of zoom.</p><h4>The service blueprint charting the way forward</h4><p>When we looked across the two blueprints we could also identify user actions that were missing and the in-product components needed to bring the new service to life.</p><blockquote>This helped us identify what new features needed to be built and what entirely new projects needed to be kicked off in order to get the school purchasing service running.</blockquote><p>We were ultimately able to use this as a starting point for our product roadmap.</p><p>The service blueprint of our vision also helped communicate all the interactions and dependencies of this service concept to other teams at Clever. At the time, another team at Clever was also working on the way district administrators purchase IT tools, and using a service blueprint to anchor our conversations made it easier to picture where and how existing and future ideas could fit within our service vision.</p><blockquote>As a result, we were able to have more meaningful conversations with stakeholders and others outside of our immediate team.</blockquote><figure><img alt="A collection of sticky notes organized into a service blueprint showing what the school purchasing process looks like through the Clever App Store." src="https://cdn-images-1.medium.com/max/1024/1*7xUJFWlw98Eht_pJF_bsYA.png" /><figcaption><em>The service blueprint of our vision for school purchasing</em></figcaption></figure><h3><strong>Evaluating our service in an international context</strong></h3><p>In addition to mapping school purchasing in the Clever App Store, we’ve also used service blueprints at Clever to develop a deeper understanding of how our overall service model performs in contexts outside the US. Although up until now Clever’s products and services have focused exclusively on customer needs in the US, we recently developed an interest in which international needs we were best positioned to serve.</p><p>To feed this curiosity, we set out to discover if our current service model would meet the needs of international markets that looked relatively similar to the US. Given the cultural similarities and shared use of English as the primary language spoken in schools, we chose the UK and Australia as the first countries to investigate. However, in order to effectively evaluate how our service model performed in these international contexts, we needed a complete understanding of the service we intended to measure. That’s where service blueprinting came in.</p><p>Since we wanted to test if schools in the UK and Australia could easily onboard to Clever and use at least one product they were interested in, we set our focus on evaluating the various product and service channels that facilitated a new customer joining Clever.</p><p>Our first step was to map out the three channels that comprise our service when a new customer wants to join Clever:</p><ul><li>customer actions (what the customer does)</li><li>Clever frontstage actions (what the customer sees)</li><li>Clever backstage actions (what the customer doesn’t see, but supports the overall service).</li></ul><p>To accurately map these three channels, we interviewed internal stakeholders from teams across the company who support any frontstage or backstage actions, including customer success, district onboarding, customer education, data analytics, product, engineering, and design. With the input of these cross-functional stakeholders, we developed the first draft of our service blueprint and, in so doing, developed a clearer understanding of the service we intended to evaluate in an international context.</p><figure><img alt="A collection of sticky notes organized into a service blueprint showing what the customer, frontstage, and backtage actions look like in an international context." src="https://cdn-images-1.medium.com/max/1024/1*rOQXUKaFVJk8yZtjkfi2fw.png" /><figcaption><em>A piece of the first draft of our international service blueprint, which focused on customer, frontstage, and backstage actions</em></figcaption></figure><p>With our service mapped out, we then met with school customers in the UK and Australia who expressed interest in using Clever to see how well our service supported getting them access to the products they wanted to use. To get a clear picture of how well our onboarding service was performing, we recorded customer feedback during pre and post onboarding interviews, reviewed email exchanges with our support teams, and tracked product analytics through the in-product onboarding funnel.</p><p>After reviewing the onboarding experience for seven Australian and four British school customers we saw a clear trend emerge: the majority of these customers were from single schools, which did not align well with Clever’s onboarding service that had been optimized for mid-sized to large US school districts with mature technical infrastructure and IT teams.</p><p>To support this theme, we added two new rows to our service blueprint that tracked specific customer pain points and the corresponding opportunities Clever had to address them.</p><figure><img alt="A collection of sticky notes organized into a service blueprint showing what pain points and opportunities look like in an international context." src="https://cdn-images-1.medium.com/max/1024/1*cZkNU1grsKa3kIqCza1P_Q.png" /><figcaption><em>A piece of the second draft of our international service blueprint, which focused on customer pain points and opportunities</em></figcaption></figure><p>Once the service blueprint reflected what we had learned from our international customers, we met again as a cross-functional team to review the findings, share thoughts, and determine our next steps.</p><p>Ultimately, this service blueprint discussion led to three initiatives that continue to shape Clever’s approach to international customer onboarding:</p><ol><li>Create an MVP of a new, simplified service that targets the needs of single schools</li><li>Re-evaluate how we ingest data for smaller school organizations</li><li>Begin to shift our language away from technical, US-centric terminology that makes navigating our onboarding service difficult for international customers</li></ol><h3><strong>How to create your own service blueprint</strong></h3><p>To get the whole picture of a customer’s journey, here are the steps to create a service blueprint:</p><ol><li><strong>Write a scenario that captures what a specific customer would want to achieve using your service</strong>. In our examples, this was a school administrator in the US trying to purchase new curriculum tools for their schools and an administrator at an Australian or British single school trying to get started on Clever.</li><li><strong>Map out the customer actions, frontstage actions, and backstage actions needed to ensure the customer achieves their goal.</strong> In our examples, we interviewed internal stakeholders from every team that touched any of these three channels.</li><li><strong>Evaluate how well your current service enables customers to achieve their goals.</strong> In our examples we looked at app store and international customer data to evaluate the efficacy of our services.</li><li><strong>Identify customer pain points and areas of opportunity.</strong> In our examples, we highlighted that school administrators in the US had trouble purchasing educational technology and international single school customers had a difficult time understanding our technical, US-centric onboarding process.</li><li><strong>Make recommendations for further action</strong>. In our examples, we recommended a redesign of the Clever app store purchasing flow and an international MVP focused on a simplified version of Clever for single schools.</li></ol><p>You can also check out these resources to help you create a service blueprint:</p><ul><li><a href="https://www.figma.com/file/JRG91cLckLSR6jijmoohKG/Service-Blueprint-Template-%5BMake-a-copy%5D?node-id=0%3A1&amp;t=HaZfbV2JU6RpwSta-1">Clever’s Service Blueprint Figma Template</a></li><li><a href="https://medium.com/capitalonedesign/download-our-guide-to-service-blueprinting-d70bb2717ddf">A Guide to Service Blueprinting by Adaptive Path</a></li><li><a href="https://www.nngroup.com/courses/service-design/">Nielsen Norman Group’s Service Blueprinting Course</a></li><li><a href="https://www.slideshare.net/KuldeepKulshreshtha/take-a-holistic-view-of-your-product-with-service-blueprints-at-uxsea-summit-2018">UXSEA 2018 presentation on Service Blueprints by Benjamin Bowes</a></li></ul><p><a href="https://www.linkedin.com/in/snehavrao/"><strong><em>Sneha Rao</em></strong></a><em> and </em><a href="https://www.linkedin.com/in/nicholas-friebel/"><strong><em>Nick Friebel</em></strong></a><em> are both teachers turned designers who work at </em><a href="https://clever.com/"><strong><em>Clever</em></strong></a><em>, an EdTech company focused on unlocking digital learning for all students.</em></p><p><em>The </em><a href="https://www.linkedin.com/company/ux-of-edtech/"><strong><em>UX of EdTech</em></strong></a><em> Community’s purpose is focused on helping UX practitioners who work on products and services that support learning. We also welcome educators, founders, and those in other disciplines looking to develop a UX mindset applied in the industry of education and future of learning and work.</em></p><p><a href="https://uxedtech.substack.com/"><strong><em>Subscribe</em></strong></a><strong><em> </em></strong><em>to our newsletter for more UX resources supporting EdTech startups and founders.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=55904419ddce" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ux-of-edtech/service-blueprinting-in-edtech-clevers-journey-55904419ddce">Service Blueprinting in EdTech (Clever’s Journey)</a> was originally published in <a href="https://medium.com/ux-of-edtech">UX of EdTech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What samurai can teach us about UX]]></title>
            <link>https://uxdesign.cc/what-samurai-can-teach-us-about-ux-6a2319283178?source=rss-25eebc7a02a4------2</link>
            <guid isPermaLink="false">https://medium.com/p/6a2319283178</guid>
            <category><![CDATA[t]]></category>
            <category><![CDATA[ux-strategy]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Nick Friebel]]></dc:creator>
            <pubDate>Mon, 16 Sep 2019 02:06:26 GMT</pubDate>
            <atom:updated>2019-09-29T00:30:56.430Z</atom:updated>
            <content:encoded><![CDATA[<h4>Wisdom from the Sengoku era on being better designers.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jt3o-xMbKCav0YMxfvVl6g.jpeg" /><figcaption>Image: <a href="http://www.twcenter.net/forums/showthread.php?551960-Saints-and-Heroes-pack-available-soon-for-Shogun-2/page4&amp;styleid=41">Total War Center Forums</a></figcaption></figure><p>Although UX design is a relatively new moniker coined in the last 30 years, the principles behind UX are as old as humanity itself. As a result, human history is replete with wisdom UX designers can draw upon today. Of all the cultures and eras that make up human history, the samurai of Sengoku era Japan offer a uniquely relevant perspective on the principles of UX through the lens of war. Their battlefield is our design sprint, their army is our design team, and their clan is our user. Although the history of the samurai is vast, I have chosen just five kernels of wisdom that UX designers can learn from in hopes that we build a better future by reflecting on the past.</p><blockquote><strong>“Those who cling to life die. Those who defy death live.”</strong></blockquote><blockquote><strong>— Uesugi Kenshin</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/744/1*rKHFJZ2mavbLmwisls_kKQ.jpeg" /><figcaption>Uesugi Kenshin. Image: <a href="https://commons.wikimedia.org/wiki/File:Uesugi_Kenshin_by_Kuniyoshi.JPG">Wikimedia Commons</a></figcaption></figure><p>Kenshin was both a warrior and the lord, or daimyo, of Echigo province. He is remembered as one of the most powerful daimyo of the Sengoku era and was known for his mastery of the battlefield. Here Kenshin is of course referring to death literally in the context of battle. In essence, he believes that samurai who fear death, and cling hopelessly to life in battle, will ultimately be defeated by their enemies.</p><p>If we replace the battlefield with a design sprint, a designer can learn from Uesugi in the same way a samurai might have centuries ago. We can best position ourselves as designers to learn from Kenshin if we frame our reading of this quote around the concept of creative maturity. If you fear feedback on your designs, and are unwilling to iterate because you are convinced your design is the only viable option, you have not achieved creative maturity. However, if you develop creative maturity, or become open to the idea that your design will have to dramatically change after prototyping, usability testing, and feedback, your design will in effect “defy death”. The iterations of your design will die, but the final product will live on stronger having gone through the iterative process.</p><blockquote><strong>“Men are your castles; men are your stone walls; men are your moats. Fellow feeling is your ally; enmity is your enemy.”</strong></blockquote><blockquote><strong>— Takeda Shingen</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2pkDDJ-adMguythmjjpBDA.jpeg" /><figcaption>Takeda Shingen. Image: <a href="http://visipix.com/cgi-bin/view?userid=1616934267&amp;q=%272aAuthors/K/Kuniyoshi%201797-1861%2C%20Utagawa%2C%20Japan%27&amp;n=445&amp;p=22&amp;l=en&amp;u=2&amp;ub=1&amp;k=1">Visipix</a></figcaption></figure><p>Kenshin’s main rival and fellow daimyo, Takeda Shingen, famously never built a castle in his province, Kai, insisting that his men were his castle. Shingen strongly believed that people were his greatest strength and therefore saw no need to build a castle as most other daimyo had done throughout the Sengoku era.</p><p>From a UX perspective, Shingen’s words can be read from the lens of empathy. Specifically, how empathy with users strengthens a product, particularly as a product grows bigger, stronger, and more popular. Rather than build the walls of your company’s castle, focus on the people that made your product what is has become. The more a company can harness the power of empathizing with users, or treating them as the castle that supports the product, the more successful that company can be. Maintaining Shingen’s “fellow feeling” for users and avoiding “enmity” throughout a product’s growth is of utmost importance because the more castle walls you build between you and your users, rather than treat them as the castle itself, the less likely you are to offer them a meaningful experience.</p><blockquote><strong>“When you put your life on the line, you want all your weapons to be of use. Your real intent should be not to die with weapons worn uselessly at your waist.”</strong></blockquote><blockquote><strong>— Miyamoto Musashi</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/813/1*-XXJfBY8okO6PHu41rqeRw.jpeg" /><figcaption>Musashi Miyamoto. Image: <a href="https://commons.wikimedia.org/wiki/File:Musashi_ts_pic.jpg">Wikimedia Commons</a></figcaption></figure><p>Although Musashi was not a samurai in the strictest definition of the term, as he worked as a freelance warrior, or ronin, rather than serving a lord, he is often considered one of the greatest warriors of the Sengoku era.</p><p>As UX designers, we can read Musashi’s words about weapons in terms of tools. While samurai used swords, daggers, spears, bows, and arrows, the list of tools a designer might use is seemingly endless and ever growing. Every year a new collection of design tools are released, some short-lived hype emerges for each, the next tool hits the market, and the cycle repeats. As designers, we can jump on the next hot tool as soon as it’s released, but if this constant jumping from tool to tool conflicts with mastery of them, then they will not be of any use. Rather, by learning a few tools to mastery and then changing tools only when it becomes necessary, not for novelty, these tools will not be “worn uselessly at your waist”, but will instead serve you as best they can in your design pursuits.</p><blockquote><strong>“Draw out what your subordinates have to say, and listen to them well. It is common knowledge that gold lies underground.”</strong></blockquote><blockquote><strong>— Nabeshima Naoshige</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/590/1*g4yCTkdM41BNtOyRvCKC_A.jpeg" /><figcaption>Nabeshima Naoshige. Image: <a href="http://www.nabeshima.or.jp/main/23.html">nabeshima.or.jp</a></figcaption></figure><p>During the Sengoku era, Naoshige served as a samurai for the daimyo of Hizen province and was known for being a fierce warlord with a sharp intellect. His wisdom is famously recorded in the practical and spiritual guide for samurai, the Hagakure.</p><p>Naoshige’s words can be read by designers in many ways as active listening is a core component of the design process. However, I think this particular quote speaks most directly to the listening that should take place amongst colleagues. Although Naoshige recommends we listen to our “subordinates”, this term may only be appropriate for designers in senior or management positions. However, I believe the term “subordinates” could be extended to include colleagues of all positions as the value of one’s insights is not determined by their position or rank on a team. Thus, by including as many colleagues as possible in the design process: designers, engineers, product managers, and listening to them well, the “gold” that “lies underground” can be uncovered and applied to the product being designed. By hearing from as many colleagues as possible who represent as many perspectives as possible, we set up our designs to be more complete in approaching the problems they intend to solve.</p><blockquote><strong>“Honor always wins, it is inevitable.”</strong></blockquote><blockquote><strong>— Ishida Mitsunari</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O7WkkVWM0mjOw5AeYmyU6Q.jpeg" /><figcaption>Ishida Mitsunari. Image: <a href="https://commons.wikimedia.org/wiki/File:Ishida_Mitsunari.jpg">Wikimedia Commons</a></figcaption></figure><p>As a samurai, Mitsunari served famed daimyo Toyotomi Hideyoshi and led Toyotomi’s Western army as commander in the Battle of Sekigahara, which was the second to last major battle of the Sengoku era. Although he was ultimately on the losing side of this battle and was executed in Kyoto, Mitsunari is remembered as an adept strategist and military leader.</p><p>Here, Mitsunari’s words are referring to honor in the context of battle as he believed that those who lived and fought honorably would ultimately prevail over those who did not. Ironically, Mitsunari did not live by these words himself and behaved dishonorably in a number of ways throughout his lifetime. For example, during the lead up to the Battle of Sekigahara, Mitsunari kidnapped the wives of his opponent’s supporting daimyo as an act of provocation rather than confront the daimyo directly. However, despite not living by his own words, Mitsunari’s defeat reflected their meaning in that by living dishonorably himself, he did not come out of the Sengoku era’s penultimate battle victorious.</p><p>As UX designers, we can read Mitsunari’s words from the perspective of design ethics. As a brief overview of what design ethics are, CC BY 4.0’s hierarchy defines ethical designs in three main categories: Human Rights (decentralized, private, open, interoperable, accessible, secure, and sustainable); Human Effort (functional, convenient, and reliable); and Human Experience (delightful). In essence, these core components seek to guide designers towards creating products that serve the user, not manipulate them. We should always be mindful of design ethics because, when building a design, we yield great power in guiding the decisions and behavior of our users. Those who use this power honorably, or ethically, will prevail over those who do not in that these designers aim to build a powerful and lasting experience for the user, not an experience that tricks the user into doing something they would not otherwise do. Although unethical designers can procure short-term gains with their products, the products that stand the test of time are designed honorably and ethically. Thus, if we abide by the principles of ethical design, the success of our products may not be “inevitable”, but the products themselves will ultimately serve our users far better than if we had not.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/253/1*tW1bty0Pm2NDynv9XJlAdg.jpeg" /><figcaption>The code of the samurai, or “bushido”. Image: <a href="https://www.orientaloutpost.com/proddetail.php?prod=cs-bushido-ldq">Oriental Outpost</a></figcaption></figure><p>In sum, whether you are a freelancing ronin or work in-house serving your corporate daimyo, we can all learn from the Sengoku era samurai and live a life more aligned with the UX bushido.</p><p><strong>References</strong></p><ul><li>The Samurai Archives (2019). <em>The samurai archives Japanese history page</em>. Retrieved from: <a href="https://www.samurai-archives.com/">https://www.samurai-archives.com/</a></li><li>Wilson, W.S. (2015). <em>The pocket samurai</em>. Boston, MA: Shambhala Publications, Inc.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6a2319283178" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/what-samurai-can-teach-us-about-ux-6a2319283178">What samurai can teach us about UX</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Design Process Never Ends, You Just Run Out of Time]]></title>
            <link>https://blog.prototypr.io/the-design-process-never-ends-you-just-run-out-of-time-92fe074c7c10?source=rss-25eebc7a02a4------2</link>
            <guid isPermaLink="false">https://medium.com/p/92fe074c7c10</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[general-assembly]]></category>
            <dc:creator><![CDATA[Nick Friebel]]></dc:creator>
            <pubDate>Mon, 01 Jul 2019 04:31:18 GMT</pubDate>
            <atom:updated>2019-10-25T19:49:27.269Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>The design process never ends, you just run out of time</strong></h3><p><em>What I learned from my first project during the General Assembly UXDI course</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gr9GXpA8c502N3UQhFFPtA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@sonjalangford?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Sonja Langford</a> on <a href="https://unsplash.com/s/photos/time?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h4><strong>The Design Process</strong></h4><p>For my first project in the General Assembly UXDI course I was tasked with designing a mobile app that sought to help alleviate a problem in another student’s life. To approach this design I conducted numerous user interviews, refined the results of these interviews into a single problem statement, developed a hypothesis for a solution, sought inspiration through competitive and comparative analyses, created initial sketches of multiple concepts, narrowed down the sketches to one concept based on user feedback, translated that concept into a paper prototype, conducted prototype testing to gain insights from user feedback, and iterated the prototype based on the test results and user feedback.</p><p>Although this process involved many steps, we had only four days to complete the project. Therefore, the design process had to be rapid yet comprehensive. As design thinking is new to me, the experience was profoundly instructive in a principal central to design thinking: you may never feel like you are finished, but as soon as time runs out, you are. As a consequence, this project’s core value was showing students that the more time you spend figuring out the root of the problem, the easier it will be to design the solution. If you develop a more complete understanding of the problem, you will be less attached to each iteration you produce and thus be able to spend more time focused on how these iterations bring you closer to a solution. In essence, as you design this solution, you will have to let go of what you <em>want to be</em> true — usually disguised as your initial designs — and open your mind to the idea that what <em>is</em> true will require you to throw away what you’ve created and iterate based on what you learn from users. The final iteration you arrive at will likely not be the <em>true</em> solution, but it will bring you closer to the truth once the clock runs out.</p><h4><strong>Meet Emily</strong></h4><p>So who was this design process focused on? Meet Emily. She is a young woman living in California training for a bodybuilding competition that will take place in the spring of 2020. She has a coach who designs her workout plans, which he published on a website that Emily can access on her smartphone while she works out. Although the coach designs these workout plans for Emily, he is not with her at the gym when she performs the workouts. Rather, he and Emily only meet twice a week to review her workout progress and recalibrate her workout plan.</p><p>As you might imagine, the workout plan is not working out. Sometimes Emily forgets how to perform a certain exercise listed on her workout plan while at the gym. Her current solution is to bring up Youtube on her phone, search for a video that demonstrates the exercise she has forgotten, watch the demonstration, then continue with her workout. Clearly, this is not an ideal solution and presents a central pain point in Emily’s workout: she is taken out of “the zone”. Although entering “the zone” is different for all of us, undoubtedly we have all experienced it at some point in our lives. The activities that get us into the zone are as varied as people’s interests, but the zone itself remains the same regardless of how entering it occurred. In the zone you are focused on one activity at a level that enables you to perform in a way you could not believe was possible until you are performing at “zone” capacity. To have something break you out of the zone is supremely frustrating and, more saliently, a tragedy in achievement and performance.</p><p>Emily’s current Youtube solution may be tenuously effective, but its impact on taking her out of the zone is unforgivable. When searching for unknown exercises she must switch between her workout plan website and the Youtube app, which on its own wastes time, but the search itself of an appropriate demonstration video only magnifies the amount of time she must subtract from actually working out. Further, once Emily has found a suitable video, the moment she hits the play button any music she might be listening to during her workout is immediately cut off, only to be replaced by the sound of whichever Youtube video she has selected. With all of these distractions at play, I knew PUMP’s primary goal would be to keep Emily in “the zone”.</p><h4><strong>Getting Emily Back in The Zone</strong></h4><p>Everything I learned about Emily’s background was gleaned from user interviews I conducted with her. In addition to the background information above, the major takeaways from these interviews were: Emily needs an exercise plan in one place on her phone; forgetting an exercise should not interrupt her workout; reviewing an exercise must be intuitive and quick; she needs to stay in the zone during her workouts no matter what.</p><p>From these key takeaways, I distilled Emily’s case into a single problem statement and a hypothesis as to how I thought I could offer a solution. At this formative stage, I was beginning to develop an idea of what my app might be able to do. With Emily’s background and needs in mind, I decided PUMP would be an appropriate name for an app that would seek to help Emily, and other bodybuilders, stay in the zone during their workouts and get pumped.</p><p><strong>Problem: </strong>Emily needs a way to remind herself how to do certain exercises at the gym because she does not want to lose focus and waste time while working out.</p><p><strong>Solution: </strong>I believe that by designing PUMP, which provides Emily with explanations of exercises built into her workout plan, I will make her workout more focused and enjoyable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*uNixhMcPYgC2VrR6" /><figcaption><em>To capture my first vision of what PUMP could offer Emily, I quickly sketched a storyboard.</em></figcaption></figure><h4><strong>Inspiration</strong></h4><p>Once I had a tentative understanding of how I could best serve Emily’s needs, I conducted a competitive and comparative analysis to seek inspiration. For my competitive analysis I reviewed three apps that focused exclusively on weightlifting: STRONG, fitbod, and JEFIT. To supplement this competitive analysis and gain a greater understanding of exercise apps in general, I reviewed two apps that focused on yoga and stretching, respectively: Daily Yoga and SWORKIT.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*UxDM1yIpbDLLMHQ2" /><figcaption><em>The competitive and comparative analyses chart. The four core features I drew most inspiration from are circled in black.</em></figcaption></figure><p>Although there were many useful features across all five apps, only four core features stood out to me as the most useful for Emily if she was to use PUMP. Further, these four core features could be broken into two categories that more directly serve Emily’s needs. First, Emily would need to create a workout plan in PUMP with her coach during one of their two-week meetings. The features that best serve this need are the ability to add custom workouts and the ability to input weight, sets, and reps for each exercise in the workout. Second, Emily would need to actually use the workout plan once she was at the gym. The features that best serve this need are visuals of the exercises, either as animations, GIFs, or videos; and a written explanation of each exercise.</p><p>Once I had determined which core features would inform the design of my app, I looked at which app implemented which feature most effectively. In terms of creating workouts with her coach, I thought fitbod provided the best version of an “add a custom workout” feature. Although all of the apps had built in exercise search lists, fitbod was the only one that gave the user clear feedback when an exercise was selected (the check mark on the image). Further, I liked how the “add exercise” button appeared in bright red at the bottom of the screen and updated from “1” to “2” when another exercise was chosen. The population of the button in bright colors when exercises were selected clearly communicated to the user that they are to press this button when they are done adding exercises to their custom workout. As I selected exercises, I visualized Emily sitting down with her coach and seamlessly adding exercises to their custom workout together.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*u-csEtpF0Q6fFIRi" /><figcaption><em>The exercise selection process of the “add a custom workout” feature in fitbod.</em></figcaption></figure><p>Once I decided on how to add exercises to a custom workout, it was time to decide how Emily and her coach would input weight, reps, and sets for each exercise. I found fitbod to be a little clunky and difficult to use as it auto-selected “reps” right away without the user being able to decide where they wanted to input a number. Further, fitbod started with a default of 3 sets and wouldn’t let you reduce the amount. However, STRONG allowed the user to decide where they wanted to input data and did not auto select any field once the window opened. Additionally, the sets began at one and could be adjusted to any number. Finally, whereas fitbod required the user to click each field input individually, the STRONG app included a “next” button on the keyboard to allow the user to easily switch between input fields. This improved the efficiency of the app and made it easier to use.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ly4NsWot6-DFNRdC" /><figcaption><em>The feature that enabled a user to input weight, sets, and reps in STRONG was more efficient and versatile than the feature in fitbod.</em></figcaption></figure><p>Now that I had my inspiration for how Emily and her coach would create custom workouts, I turned my focus to how the app would be used in the gym. I liked how JEFIT had a GIF visual of each exercise at the top of the screen during each workout. This would be easy for Emily to see a workout and would be the first step to keeping her in the zone if she forgot how to do an exercise. Although, if Emily needed more detail on how to do an exercise, I wanted her to be able to get a step-by-step guide in a modal window. STRONG had just that. If an exercise is selected, a modal window opens with both a GIF of the exercise and a written step-by-step guide. Therefore, I tentatively planned to combine JEFIT’s in-workout screen layout with STRONG’s more detailed explanation on a given exercise in a modal window.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zWo01SSWvqkcpvRv" /><figcaption><em>I sought to combine JEFIT’s in-workout screen with a more detailed explanation of a workout modeled after STRONG’s modal window explanation of exercises.</em></figcaption></figure><h4><strong>Initial Sketches and Refinement</strong></h4><p>Once I had a working concept in mind, I began sketching out some rough ideas of how PUMP might look and work. After receiving Emily’s feedback, I identified three sketches that best represented her needs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2LtLqX43I9VNLFj0" /><figcaption><em>I refined my initial sketches down to three main ideas.</em></figcaption></figure><p>In the first of these sketches, pictured above in the upper left hand corner, I decided to design my during-workout screen such that it included a visual representation of the workout at the top of the screen as inspired by JEFIT, but would include a timer and “end-workout” button as inspired by fitbod. In the second of these sketches, pictured above directly to the right of the first sketch, I decided to include visuals of the exercises during the custom workout creation so that familiarity with each exercise would be front loaded to Emily during the workout creation process. Finally, in the final sketch, I included a modal window to further explain step-by-step how an exercise could be performed, as inspired by STRONG.</p><h4><strong>Prototype Testing</strong></h4><p>With a clearer understanding of what PUMP would look like, I began working on the paper prototype. The prototype itself would function as a rough version of PUMP so that I could test the functionality of the app’s core features. Through testing, I could deduce what aspects of PUMP worked well and what needed improvement to best meet Emily’s needs.</p><p>During the first section of the paper prototype I wanted to simulate what it would be like for Emily to meet with her coach and create a new custom workout together. For Emily to have her coach’s workout plan in one place on her phone, she and her coach would have to create a plan together using PUMP during one of their meetings. Thus, I wanted to first prototype how the process of adding a custom workout would go. The first three screens are dedicated to adding a new workout and naming that workout. I wanted the layout to be as simple as possible to maximize learnability and efficiency.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*I-Jx8_9DEKgZZG8b" /><figcaption><em>Naming a new custom workout in the paper prototype.</em></figcaption></figure><p>Once Emily and her coach had created a new workout, I wanted them to easily be able to add exercises to the workout. I decided to use design patterns inspired by fitbod and the apple contacts list to design the exercise search menu. I intentionally had my prototype testers look for an exercise off-screen (dumbbell bench press) so I could observe how they decided to find it. Participants both used the search menu and scrolled to find the exercise, as I had hoped. This was a valuable insight from prototype testing because making both search and scroll available would be important to communicate to developers during the development phase.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JP7sKQMRU3jAB-N7" /><figcaption><em>Selecting exercises for a custom workout in the paper prototype.</em></figcaption></figure><p>During the second part of the prototype I wanted to simulate how Emily might use this newly created workout once she was at the gym. With inspiration from the fitbod app, I included a large “start workout button” to make the entry to the workout as seamless and intuitive as possible. During the workout, I told my prototype testers that they forgot how to do a dumbbell bench press to see how they would try to review the exercise. Everyone was able to access the modal window with a more detailed description of the exercise, however participants got to the screen in different ways. Some tapped the “how to” button in the lower left corner of the image at the top of the screen, while others tapped the image itself. This was important feedback to take note of so that during the development phase both options could be made available. I was pleased to see that all participants were easily able to access the “how to” modal review window as this is one of the core features of the app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6u0Ue1VPuSOIB31m" /><figcaption><em>Starting a workout and reviewing an exercise in the paper prototype.</em></figcaption></figure><h4><strong>Prototype Iteration</strong></h4><p>After testing the prototype, feedback from the users, and my observations of user behavior, informed my iterations of the prototype’s design. The first piece of feedback I got was with regard to the tone of the app. While using the “how to” modal window, one of the participants said it would be nice to be validated and motivated once they had finished reviewing the exercise. Thus, I added a “Got it!” button for users to tap to close the window rather than just the “x” in the upper right hand corner.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qE4EaRdhwn3RR44C" /><figcaption><em>The “Got it” button I added to the prototype based on user feedback.</em></figcaption></figure><p>The most critical feedback I got on my prototype was from Emily herself. After creating a workout she asked if that workout would be saved for future use and could be accessed again. I said it would, but that it was not apparent based on the flow of the prototype. To make the fact that the workout had been saved, and could be accessed for future use, I included a brief pop-up that would populate after the “done” button had been pushed when creating a new workout.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LHec7W2j0xe_AQMx" /><figcaption><em>A pop up window I added to the prototype based on user feedback.</em></figcaption></figure><p>To expand upon the idea of saving workouts and coming back to them in the future, I designed a path to get back to workouts you have already created by selecting “my workouts” from a drop down navigation menu. I also designed how you could access previously created workouts from the home screen as well. By having multiple ways to intuitively access previously created workouts, it is my hope that Emily will be able to easily choose from any workout she has created in the past.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5pHhxEhntRmQObMe" /><figcaption><em>A path to “My Workouts”.</em></figcaption></figure><h4><strong>Next Steps</strong></h4><p>By the end of the four day sprint I believe I had helped to address two main facets of Emily’s problem. First, I had enabled her and her coach to create a custom workout plan in advance to be housed in one app. Second, I had provided a way for Emily to review forgotten exercises within the same app. However, based on Emily’s feedback following the prototype iteration phase, I still need to design a way for her to track how past workouts compare to present workouts. To meet this need, I can develop a workout summary feature that focuses on comparing workouts through time.</p><p>In all, the biggest takeaway from this first project was that it showed me what the design process feels like in practice. It is a messy and, at times, frustrating process as it places more emphasis on the problem than on the solution. Consequently, much of your time is spent in the thick of the problem with no clear answer in sight. Rather than arrive at <em>the </em>solution, you design iterations with that problem in mind knowing that these tentative solutions will have to be scrapped and replaced to come as close to a solution as time permits. In short, the design process never ends, you just run out of time.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff51076%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Ff51076&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/ed6399974de6e1c6fa5f3851dd966fad/href">https://medium.com/media/ed6399974de6e1c6fa5f3851dd966fad/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=92fe074c7c10" width="1" height="1" alt=""><hr><p><a href="https://blog.prototypr.io/the-design-process-never-ends-you-just-run-out-of-time-92fe074c7c10">The Design Process Never Ends, You Just Run Out of Time</a> was originally published in <a href="https://blog.prototypr.io/">Prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Case for Teaching: Make the Profession Desirable, Not Honorable]]></title>
            <link>https://medium.com/age-of-awareness/the-case-for-teaching-make-the-profession-desirable-not-honorable-8cd6db4b4743?source=rss-25eebc7a02a4------2</link>
            <guid isPermaLink="false">https://medium.com/p/8cd6db4b4743</guid>
            <category><![CDATA[k12-education]]></category>
            <category><![CDATA[teaching]]></category>
            <category><![CDATA[education]]></category>
            <dc:creator><![CDATA[Nick Friebel]]></dc:creator>
            <pubDate>Tue, 28 May 2019 03:17:19 GMT</pubDate>
            <atom:updated>2019-09-16T21:00:07.295Z</atom:updated>
            <content:encoded><![CDATA[<h3>The case for teaching: make the profession desirable, not honorable</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*G2mYMjx_2BlEcQqpxhH2Vg.jpeg" /><figcaption>Photo via <a href="https://images.app.goo.gl/KyV5GM9HFc2n7uEb9">simplek12</a></figcaption></figure><p>Whether we are having a casual conversation with friends, listening to a political speech, or participating in a parent-teacher conference, the way we talk and think about public K-12 teachers in this country reflects a unique cognitive dissonance. On one hand, teachers are seen as honorable public servants who sacrifice financial and professional self-interest for the improvement of our society. On the other hand, those same teachers are seen as the losers of our professional class. They are stuck in a low-earning job with no prospect of a raise beyond predetermined yearly pay increases and endure the notoriously stressful grind that is working with young people.</p><p>In his most recent Netflix special, which aired prior to his controversial press coverage in the wake of the Me Too movement, Louis C.K. addresses this cognitive dissonance surrounding our society’s school teachers with humor rooted in the ugly, yet undeniable, truth. To explore this dissonance, C.K. presents a dichotomy between how we want to view teachers and how we realistically interpret what it means to be a teacher. He begins with the former by saying, “In a democracy there’s no more noble contribution you could make than to teach in a public school.” Then, in almost the same breath he turns to the reality of being a teacher, “And in this country the people who do that, they’re f****** losers. Everybody knows it but they keep doing it. New people are teaching everyday knowing how s***** it is.” To support his point, C.K. embodies a new teacher character and questions, “How much will I be paid? About ten dollars a year. What if I get really good at it? Nothing. Nothing happens.” Despite learning these horrific details, C.K.’s new teacher character decides, “Ok I’ll try it for 25 years” (C.K., 2017). With hilarious yet sobering clarity, C.K. describes the imperfect balance that this cognitive dissonance surrounding the teaching profession produces: in the United States we dangerously rely on the goodwill of those who care enough about the future of our nation’s children to overlook the numerous and explicit downsides of being a public school teacher.</p><p>Similar to C.K.’s split interpretation of what it means to be a teacher, there is a double-speak behind the word “honorable”, or in his words “noble”, when it is used to describe a profession. While an honorable career is one that is invaluable and necessary to our society, think soldiers, nurses, policemen, and garbagemen, it is also one that very few people want as their own job. Instead of keeping teaching as an honorable profession, we should make teaching desirable.</p><p><strong>Teaching in the 21st Century</strong></p><p>Although this dubious model of relying on the goodwill of a select few to fill the teaching ranks has remained relatively viable for generations, it has done so by mostly relying on patriarchal limits of what jobs are appropriate for women, thus producing a steady and unwavering supply of teachers to join the profession (Hoffman, 2003). Although the demographics of teachers have not changed much in the last century, in 1910 roughly 80% of teachers were women while in 2012 women made up 76% of the teaching profession (U.S. Department of Education, 1993; U.S. Department of Education, 2016), the number of people willing to become teachers has significantly decreased. From 2009 to 2013 there has been a 31% decrease in teacher preparation program enrollment across the United States (U.S. Department of Education, 2015). This significant decrease in teacher preparation program enrollment in just four short years is rooted in a number of reasons, many of which are captured in C.K.’s stand-up act, but, regardless of those reasons, the decrease unequivocally communicates that fewer and fewer people are interested in teaching as we move into the 21st century. In short, the imperfect balance we’ve relied on for so long to attract new teachers is losing stability and, unless something changes, this trend will continue into the foreseeable future.</p><p><strong>How to Enact Change</strong></p><p>With this drastic decline in teacher preparation program enrollment, the question remains: if teaching is a job people no longer want, how can we attract new teachers? The answer relies on two perspectives. First, how prospective teachers view the teaching profession and, second, how society at large views the teaching profession. If, as a society, we are to redefine what it means to be a teacher from both the inside, teachers themselves, and outside, the rest of the population, then we can eliminate the cognitive dissonance that shapes our view of teachers as both honorable public servants and low-earning, professionally stagnant losers. To redefine what it means to be a teacher from the inside and out we must pivot from viewing teaching as honorable to viewing teaching as desirable.</p><p>When considering how to make teaching more desirable to young adults entering the workforce, the easy answer is to increase the size of the proverbial carrot on the stick and pay teachers more. Although paying teachers more would almost definitely encourage more people to join the teaching profession, the budgetary constraints of the public sector make this solution improbable and, frankly, unrealistic. Teaching in public schools is a public service, not a product sold by a private corporation, so the monetary rewards and incentives for teachers are significantly limited. However, if prospective teachers view the core value of the profession as the skills acquired while working as a teacher and the applicability of those skills to many careers, rather than income, the desirability of teaching may substantially shift in a positive direction. Although the number of skills teachers develop throughout their time in the profession is vast, I have selected the skills 260 major employers in the United States reported they would like to have in their 21st century workforce based on a survey conducted by the National Association of Colleges and Employers. The top five skills these employers reported to desire most for their 21st century workforce are: 1) leadership; 2) ability to work in a team; 3) communication skills (written); 4) problem-solving skills; and 5) communication skills (verbal) (National Association of Colleges and Employers, 2016).</p><p><strong>Leadership</strong></p><p>With teachers at the helm of classes ranging from 20 to 35 students, leadership quickly emerges as one of the strongest skills they develop. Not only do teachers have to manage their students’ behavior in class, they must engage the students in meaningful learning experiences, push students past fixed mindsets into growth mindsets, organize parent volunteers for special activities, and maintain model behavior themselves as they are one of each student’s primary role models. The daily leadership requirements of a public school teacher is hard to compare to other careers because the scale is so uncommon. Not many professions require you to manage 20 to 35 others your first year on the job, let alone ever. Although one might argue that those 20 to 35 people are children, not adults, and therefore cannot be compared, I would posit that if you must manage a group of people you will develop leadership skills that are not limited to age or temperament. For example, if a teacher gives an assignment to his/her class, sets a deadline, monitors progress, and helps the students as they progress through the assignment, these same skills in leading a group towards accomplishing a shared goal could easily apply to a leading a marketing team that needs to meet an advertisement deadline, leading a team of engineers as they develop a new app, or leading a business team deciding on what to include in an investment portfolio.</p><p><strong>Ability to Work in a Team</strong></p><p>Whereas teachers primarily develop leadership skills by managing their students, they develop the ability to work in a team by working alongside their grade-level or department teams. Although some might imagine that teachers are lone wolves who manage the domain of their classroom with unfettered independence, this situation is far from reality. Rather, teachers meet regularly with grade-level or department teams to lesson plan, discuss student difficulties and strengths, strategize long term projects, plan field trips, discuss budgetary issues, plan interventions with struggling students, and mentor or advise one another. These are just a few ways teachers spend their time together during team meetings. This collaboration not only makes the overall learning experience better for their students, it helps teachers develop valuable teamwork skills in a profession that is largely assumed to be a solo endeavour. As teachers mostly hone their ability to work in a team with other adult professionals, rather than young students, the applicability of this skill set to other jobs is clear. Just as teachers work in teams to manage the trajectory of a school year, investors work in teams to strategize a financial quarter and doctors work in teams to discuss unusual or rare medical conditions.</p><p><strong>Communication Skills</strong></p><p>In teaching communication is paramount as the amount and range of people you communicate with daily is vast. Outside of the classroom, the most common way teachers communicate is through email. Whether they are sent by supervisors, parents, or colleagues, teachers must stay on top of their emails daily and spend a fair chunk of their non-teaching time writing and responding to emails. These emails typically impact or affect scheduling, lesson plans, organizational strategies, student behavior, and the academic outcomes of your students. Thus, email itself can become somewhat of a juggling act. While many professionals have secretaries or admins, teachers are their own admins and spend much of their time away from students communicating electronically all the while developing their written communication skills.</p><p>In the classroom, the most common way a teacher communicates is, unsurprisingly, to his/her students. Regardless of the age of the students, a teacher must learn how to communicate clearly, concisely, and with enthusiasm because, despite the maturity of the students, the concepts the teacher communicates are almost always new to the students. Thus, teachers have to practice effective written and verbal communication daily to connect students with new and often difficult material. As adults we often take for granted that everything we say or write will be understood. However, if you are communicating with a student, you have to anticipate their misunderstandings and prepare alternative modes of communication to reiterate what was originally shared. Further, the communication teachers and students engage in often exits the realm of academics and delves into social-emotional territory. In such situations teachers must become counselors and help their students through difficult times in their lives.</p><p>This process of planning effective communication, anticipating misunderstandings, redirecting your communication style, counseling students in need, staying on top of an ever changing schedule, and responding to countless emails per day are advanced communication skills and can be applied to a number of professional settings. For example, explaining to a client the benefits of a product and how your product outperforms the competitor’s, counseling a colleague when he or she is having a difficult time in his/her professional or personal life, and promptly responding to endless emails from clients, supervisors, and colleagues.</p><p><strong>Problem-Solving Skills</strong></p><p>In nearly every career you have to please either clients, supervisors, or both. As a teacher, crafting a diplomatic balance between your clients (children and their parents) and your supervisors (principals, assistant principals, and district-level administrators) immediately becomes critical each school year and is central to teachers developing high-quality problem-solving skills. In terms of your clients, you must ensure that you are meeting the individual needs of students, which are varied and vast with each group you receive, and meeting the needs of parents, which usually consists of keeping an open line of communication, addressing each of their individual requests for their child, and maintaining a professional composure during difficult or sensitive conversations. In terms of your supervisors, you must make sure that you are meeting your regular and frequent assessment deadlines including, but not limited to: state tests, district tests, and performance reviews, while performing a host of additional duties that live somewhere between required and optional including, but not limited to: yard duty, piloting new curriculum or programs, staff meetings, professional development trainings, union meetings, committee meetings, and committee presentations.</p><p>As you might imagine, the interests of your clients and your supervisors may at times conflict. For example, if you have a district assessment deadline which aims to produce a standardized measure of your students’ academic competency, yet you have been meeting an individual student’s needs by teaching them content below what the assessment measures, you have to give the district assessment to appease your supervisors knowing your client, the student, cannot yet perform at the level the assessment requires. As a teacher, you will continue teaching this high-needs student at the level most suitable for his/her learning and develop your own formative assessments to track their progress knowing that the district assessment has not helped your efforts. Conversely, you will still use the district assessment data as a measurement tool for many other students’ progress, and the district supervisors will similarly use this data, thus preserving the value of administering the district assessment. This nuanced understanding of how to please both your clients and supervisors while still making those decisions valuable to yourself is something that teachers regularly perform and it shapes them as true problem-solvers. This is just one example of myriad situations in which teachers must employ critical thinking and problem solving to meet the demands of their profession. As problem solving is necessary in nearly every job, it is not difficult to see the applicability of this skill to a number of other professions. Regardless of what job you choose you will at some point, if not constantly, have to please your clients and supervisors while ensuring that those decisions also help you progress through your career.</p><p>If we can attract new teachers with the skills they will develop as a consequence of joining the profession, we need industry leaders outside of education to warm up to the idea that teachers are multi-talented professionals who have all of the 21st skills employers seek. If we can enact a societal shift in the way we view teachers from inside and outside the education world, the teaching profession can embody what it’s title suggests: that teaching is a profession performed by professionals.</p><p><strong>Conclusion</strong></p><p>Although some may view my proposal as something akin to Teach for America, where underprepared young college grads use a short teaching stint as a vehicle to propel their careers outside of education. This is in no way what I propose. Rather, I seek to elevate the desirability of teaching by highlighting the skills credentialed public school teachers develop throughout their time in the classroom. Thus, the ultimate goal is not to use teaching as a vehicle to join another profession, but rather it is to introduce the prospect that there is immense value to the skills you develop as a teacher which far exceed the image of a low-income loser stuck in a 25 year, monotonous career. If, as a teacher, your skills are seen as applicable beyond your career it removes the shackles of an “honorable” career and makes the career desirable. If teaching is seen as desirable, the profession will become more competitive and attract stronger talent. In turn, we will better serve our students and teachers will finally join the professional class they have been ostracized from for so long.</p><p><strong>References</strong></p><p>C.K., L. (2017). <em>2017</em>. Retrieved from <a href="https://www.netflix.com/title/80161109">https://www.netflix.com/title/80161109</a></p><p>Hoffman, N. (2003). <em>Woman’s “true” profession: Voices from the history of teaching</em>. Cambridge, MA: Harvard Education Press.</p><p>National Association of Colleges and Employers (2016). <em>Job Outlook 2016</em>. Retrieved from <a href="http://www.naceweb.org/career-developmentand-predictions/job-outlook-2016-att">http://www.naceweb.org/career-developmentand-predictions/job-outlook-2016-att</a><a href="http://www.naceweb.org/career-development/trends-and-predictions/job-outlook-2016-attributes-employers-want-to-see-on-new-college-graduates-resumes/">ributes-employers-want-to-see-on-new-college-graduates-resumes/</a></p><p>U.S. Department of Education, National Center for Educational Statistics (1993). <em>120 Years of American Education: A Statistical Portrait. </em>Retrieved from <a href="https://nces.ed.gov/pubs93/93442.pdf">https://nces.ed.gov/pubs93/93442.pdf</a></p><p>U.S. Department of Education, Office of Postsecondary Education (2015). <em>Higher education act Title II: Enrollment in teacher preparation programs</em>. Retrieved from <a href="https://title2.ed.gov/public/44077_Title_II_Issue_Brief_Enrollment_V4a.pdf">https://title2.ed.gov/public/44077_Title_II_Issue_Brief_Enrollment_V4a.pdf</a></p><p>U.S. Department of Education, National Center for Educational Statistics (2016). <em>Digest of educational statistics, 2015.</em> Retrieved from <a href="https://nces.ed.gov/fastfacts/display.asp?id=28">https://nces.ed.gov/fastfacts/display.asp?id=28</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8cd6db4b4743" width="1" height="1" alt=""><hr><p><a href="https://medium.com/age-of-awareness/the-case-for-teaching-make-the-profession-desirable-not-honorable-8cd6db4b4743">The Case for Teaching: Make the Profession Desirable, Not Honorable</a> was originally published in <a href="https://medium.com/age-of-awareness">Age of Awareness</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>