<?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 Jon Gunnison on Medium]]></title>
        <description><![CDATA[Stories by Jon Gunnison on Medium]]></description>
        <link>https://medium.com/@jgunnison?source=rss-be7b38c8ce66------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dywNCyxq5OOf5xsQNrQjbw.jpeg</url>
            <title>Stories by Jon Gunnison on Medium</title>
            <link>https://medium.com/@jgunnison?source=rss-be7b38c8ce66------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 06:40:56 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jgunnison/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[Bridging the Belonging Gap: How Every Employee Can Make a Difference]]></title>
            <link>https://medium.com/@jgunnison/bridging-the-belonging-gap-how-every-employee-can-make-a-difference-bf92d75d0d5e?source=rss-be7b38c8ce66------2</link>
            <guid isPermaLink="false">https://medium.com/p/bf92d75d0d5e</guid>
            <category><![CDATA[work-culture]]></category>
            <category><![CDATA[workplace-culture]]></category>
            <category><![CDATA[team-collaboration]]></category>
            <category><![CDATA[work-productivity]]></category>
            <dc:creator><![CDATA[Jon Gunnison]]></dc:creator>
            <pubDate>Wed, 28 Aug 2024 13:35:29 GMT</pubDate>
            <atom:updated>2024-08-28T13:35:29.453Z</atom:updated>
            <content:encoded><![CDATA[<p>In today’s corporate world, there’s a hidden gap that’s costing businesses dearly: the belonging gap. Picture this: you walk into work every day feeling disconnected, unseen, and unvalued. How do you think you might perform under these conditions? Unfortunately, this is the reality for many employees.</p><p>When people truly feel they belong, productivity soars, morale skyrockets, and talented staff stick around. This isn’t just about organizational change; it’s about empowering individuals to create positive change for their coworkers and entire organizations.</p><p><strong>The Power of Belonging</strong></p><p>Imagine logging in for a remote meeting or walking into your workplace and feeling truly seen, valued, and safe to express yourself. That’s belonging in a nutshell. It’s not just a warm, fuzzy feeling; it’s the outcome of how people treat each other, and it has a massive impact on your work life.</p><p>Consider Sarah, a new hire at a tech startup. On her first day, her teammate Jake noticed she looked a bit lost. He introduced himself, showed her around, and invited her to lunch with the team. By the end of the day, Sarah felt welcomed and part of the group. That’s belonging in action.</p><p>When employees feel like they belong, everything changes. They’re more likely to speak up in meetings, share innovative ideas, and collaborate effectively with their colleagues. They’re also less likely to call in sick or start looking for a new job.</p><p><strong>Connection: The Heartbeat of a Thriving Workplace</strong></p><p>Connection in the workplace goes beyond just knowing your colleagues’ names. It’s about truly understanding who they are as people. It’s the shared experiences, the inside jokes, and the knowledge of each other’s lives outside of work that create a sense of community.</p><p>Take Amanda, for example. She’d been with her company for a year but always felt like an outsider. That changed when her team started a weekly coffee chat. During these informal gatherings, Amanda learned about her colleagues’ lives outside of work, and suddenly, she felt part of something bigger.</p><p>When you feel connected to your team, you’re more likely to collaborate effectively, share ideas, and go the extra mile to help each other out. It’s not just about ticking boxes on a to-do list; it’s about working towards shared goals with people you care about.</p><p><strong>Respect: The Foundation of Belonging</strong></p><p>Respect isn’t just about politeness or professional courtesy. It’s about truly valuing each person for who they are and what they bring to the table. When you feel respected, you’re more likely to share your ideas, take initiative, and go above and beyond in your work.</p><p>Consider Salwa, a marketing specialist who always felt her ideas were overlooked. One day, her manager started actively seeking her input in team meetings. This simple act of respect transformed Salwa’s experience at work, boosting her confidence and creativity.</p><p>Respect also extends to recognizing the whole person, not just the employee. For instance, when Tom’s colleagues supported his need to leave early for his daughter’s school events, he felt a deeper sense of belonging to his workplace community.</p><p><strong>Protection: Ensuring a Safe Environment for All</strong></p><p>Protection in the workplace goes beyond physical safety. It’s about emotional and psychological well-being too. It’s about creating an environment where you can thrive without feeling vulnerable or exposed.</p><p>Mei used to dread team meetings, afraid that her ideas would be shot down or ridiculed. But her new manager, Ben, changed the dynamic by introducing a no-interruption rule and encouraging everyone to contribute. Suddenly, Mei felt safe to speak up, and her innovative ideas started flowing.</p><p>Creating a culture of protection isn’t just the responsibility of leadership. Everyone can contribute by treating others with respect and kindness, being mindful of their colleagues’ time and workload, and speaking up against unfair treatment.</p><p><strong>Energizing the Workplace Through Belonging</strong></p><p>Have you ever been part of a team where everything just clicked? Where ideas flowed freely, everyone supported each other, and you couldn’t wait to get to work each day? That’s the energy of belonging in action, and it’s a powerful force in the workplace.</p><p>This energy isn’t just a feel-good concept; it’s a tangible force that drives engagement, creativity, and productivity. When you feel a strong sense of belonging, you’re more likely to bring your best self to work and produce your best results.</p><p>Remember, fostering a sense of belonging isn’t just the responsibility of leadership — it’s something everyone can contribute to. By making others feel connected, respected, and protected, you’re adding to the positive energy in your workplace.</p><p><strong>Conclusion: The Power is in Your Hands</strong></p><p>By fostering connection, showing respect, and protecting your colleagues at work, you can build a culture of belonging that energizes your entire team. Grand gestures are great, but it’s the small, daily actions that make the biggest difference — from welcoming new colleagues to standing up against exclusion or bullying. When people feel they truly belong, they’re more engaged, creative, and productive, leading to better results for everyone.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf92d75d0d5e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What’s in It for Me?]]></title>
            <link>https://medium.com/@jgunnison/whats-in-it-for-me-10ca0c4fcc19?source=rss-be7b38c8ce66------2</link>
            <guid isPermaLink="false">https://medium.com/p/10ca0c4fcc19</guid>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[ethical-business]]></category>
            <category><![CDATA[growth-mindset]]></category>
            <dc:creator><![CDATA[Jon Gunnison]]></dc:creator>
            <pubDate>Thu, 01 Aug 2024 18:46:03 GMT</pubDate>
            <atom:updated>2024-08-01T18:46:03.859Z</atom:updated>
            <content:encoded><![CDATA[<h3>What’s in It for Me? How Businesses Can Thrive While Benefiting Society and Ensuring Sustainable Success</h3><p>In today’s world, businesses are increasingly expected to contribute positively to society while maintaining their financial health. Balancing these seemingly conflicting goals is possible by adopting a mindset that values long-term, inclusive growth over short-term gains. By prioritizing the well-being of all stakeholders — customers, employees, communities, and the environment — businesses can achieve sustainable success that benefits everyone involved.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*HBmHLmjmW-d1zAEjl6Isgw.gif" /><figcaption>Stop Motion Animation GIF by Mighty Oak</figcaption></figure><h3>Embracing the Pie-Growing Mentality</h3><p>The pie-growing mentality is a philosophy where businesses strive to expand their overall value rather than merely redistributing existing value. This approach can lead to better financial performance and societal benefits. Real-world examples show how aligning business practices with broader societal goals can create a more equitable and prosperous future for everyone.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*7pKorPrX5zxmDqJR1mWqKQ.gif" /><figcaption>School Dessert GIF by Texas Instruments Education</figcaption></figure><h3>From Profit to Purpose: A Tale of Two CEOs</h3><p>Consider the contrasting approaches of Martin Shkreli and Roy Vagelos. Shkreli, as CEO of Turing Pharmaceuticals, dramatically increased the price of Daraprim, prioritizing profits over patients’ health. This pie-splitting mentality focuses on maximizing investor returns at the expense of other stakeholders.</p><p>In contrast, Roy Vagelos, former CEO of Merck, chose to distribute Ivermectin for free to combat river blindness in impoverished communities. This decision saved millions of lives, enhanced Merck’s reputation, and ultimately benefited the company in the long run. This is the essence of the pie-growing mentality — creating value for all stakeholders and expanding overall value.</p><h3>Growing the Pie Through Effective Incentives</h3><p>Incentives play a crucial role in driving business success. Bart Becht, former CEO of Reckitt Benckiser, faced public outrage over his high pay. However, his leadership brought significant growth and innovation to the company, benefiting shareholders, customers, and employees alike.</p><p>The key takeaway is that executive pay should be linked to long-term performance, promoting investment in the company’s future. Effective incentives should focus on long-term value creation rather than merely reducing pay levels.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*f8g4fNoNJgY9YKnVR6Y82w.gif" /><figcaption>3D Success GIF</figcaption></figure><h3>The Controversial Practice of Share Buybacks</h3><p>Share buybacks, often criticized for prioritizing short-term gains, can also be strategic in a positive way. When executed correctly, buybacks can reduce future dividend obligations and signal confidence in the company’s long-term prospects. However, they should be part of a broader strategy focused on sustainable growth and societal benefits.</p><h3>Purpose-Driven Excellence in Enterprises</h3><p>Purpose-driven innovation can have a profound impact on society. Vodafone’s M-Pesa service transformed lives in Kenya by providing mobile banking to remote areas. This is an example of how aligning business operations with a broader societal purpose can yield significant benefits.</p><p>Companies like Unilever have shown that even everyday products can significantly impact global health. Their handwashing campaign improved hygiene practices worldwide, reducing pneumonia and diarrhea infections. Purpose-driven excellence is the most effective way for companies to grow the pie, benefiting both society and shareholders.</p><h3>Empowering Citizens to Shape Business Practices</h3><p>As stakeholders, policymakers, and influencers, citizens have substantial power to shape business practices. By selecting companies that align with their values, choosing ethical employers, and supporting responsible businesses, individuals can contribute to a system where businesses strive to grow the pie for everyone.</p><p>Policymakers can influence regulation to address market failures and promote environmental responsibility. Influencers can shape public opinion by highlighting both positive and negative corporate behaviors.</p><h3>Final Summary</h3><p>The key takeaway is that businesses can achieve sustainable success by adopting a pie-growing mentality. This involves integrating social responsibility into core operations, aligning executive incentives with long-term goals, and strategically using practices like share buybacks to foster growth. Empowering citizens to engage with businesses and influence their practices is also crucial. By working together, individuals and businesses can build a fairer, more sustainable economy, demonstrating that everyone has a role in growing the pie and achieving lasting positive impact.</p><p>By focusing on long-term, inclusive growth, businesses can thrive while benefiting society. This balanced approach ensures sustainable success and a prosperous future for all stakeholders.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=10ca0c4fcc19" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A New Paradigm for Leadership]]></title>
            <link>https://medium.com/@jgunnison/a-new-paradigm-for-leadership-b7673131e162?source=rss-be7b38c8ce66------2</link>
            <guid isPermaLink="false">https://medium.com/p/b7673131e162</guid>
            <category><![CDATA[team-management]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[workplace]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[leadership-skills]]></category>
            <dc:creator><![CDATA[Jon Gunnison]]></dc:creator>
            <pubDate>Wed, 24 Jul 2024 14:07:52 GMT</pubDate>
            <atom:updated>2024-07-24T14:07:52.955Z</atom:updated>
            <content:encoded><![CDATA[<p>In today’s dynamic organizational landscape, a crucial question often surfaces: Should leaders focus on value propositions or virtue propositions? This distinction is more than just a matter of semantics; it shapes how leaders approach their objectives and navigate challenges. Let’s dive into why choosing virtues over values can redefine success and lead to more sustainable growth.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*i5SlsH8nh-AhcUmFf7JiYw.gif" /><figcaption>reese witherspoon fork in the road GIF by Fox Searchlight</figcaption></figure><h3>Value vs. Virtue Propositions</h3><h4>Value Propositions</h4><p>Teams that prioritize value propositions aim to make their products, services, or images attractive in the short term. Their focus is on immediate appeal, often at the cost of integrity and honesty. While this approach might yield quick wins, it can involve cutting corners and overlooking inconvenient truths.</p><h4>Virtue Propositions</h4><p>Conversely, teams guided by virtue propositions emphasize consistent, principled improvements. These teams are anchored in moral virtues that transcend cultural and temporal boundaries, fostering true progress and sustainable success. Leaders who prioritize virtues like love, integrity, truth, excellence, and relationships build a foundation that endures beyond immediate gains.</p><h3>The Five Core Virtues</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*wMzqt1_RK_17HO0PtEgtvw.gif" /><figcaption>Typography Number GIF by Kev Lavery</figcaption></figure><h3>1. Love</h3><p>True leadership begins with love — a commitment to serving others above oneself. Virtuous leaders inspire their teams, believe in their potential, and respect every individual. They guide with compassion, even in adversity.</p><h3>2. Integrity</h3><p>Integrity is about aligning words with actions. Virtuous leaders act according to their beliefs, admit mistakes, and maintain a consistent, principled approach.</p><h3>3. Truth</h3><p>Grounded in reality, these leaders distinguish between right and wrong, fact and opinion. They stand up for what is right and speak the truth, even when it’s uncomfortable.</p><h3>4. Excellence</h3><p>Virtuous leaders reject complacency. They strive for continuous improvement, set high standards, and create an environment where everyone can excel.</p><h3>5. Relationships</h3><p>Leadership is fundamentally about people. Virtuous leaders care deeply about their teams, listen with empathy, and foster trust and rapport.</p><h4>The Integrating Virtue: Courage</h4><p>It takes courage to embody these virtues consistently and to inspire transformative change. Courage helps leaders challenge the status quo and maintain their virtuous path.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*MQJM72i-3wVG3rzd1IqyJQ.gif" /><figcaption>Spider-Man GIF by Spider-Man: Across The Spider-Verse</figcaption></figure><h3>Becoming a Servant Leader</h3><p>Great leaders understand that leadership is about cultivating motivated followers. They exemplify “servant leadership,” focusing on empowering and supporting their teams. Leaders like Dr. Paul Farmer, who worked alongside the communities he served, demonstrate how servant leadership can drive sustainable growth and innovation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*0a8zsrqBRmRgo0G2E9Gg5Q.gif" /><figcaption>Follow Me Netflix GIF by True and the Rainbow Kingdom</figcaption></figure><h3>Embracing Diversity</h3><p>Effective teams require diversity to thrive. A diverse team brings new perspectives and ideas, preventing the stagnation of groupthink. Leaders must build inclusive environments where every voice is heard and valued.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*do6RsDYYj6tz2augL5cYvg.gif" /><figcaption>Diversity Love GIF by VelvyTie</figcaption></figure><h3>Building a Leaderless Organization</h3><p>The pinnacle of virtuous leadership is creating an organization where leadership virtues are deeply embedded and widely shared. Such organizations operate like highly cooperative systems in nature, with distributed authority and shared ownership of the vision.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*GvC1iJBS6J0eri0C0zoe0Q.gif" /><figcaption>Huddle Up Go Team GIF</figcaption></figure><h3>Conclusion</h3><p>Choosing virtues over values leads to a more effective and sustainable leadership model. By grounding leadership in the core virtues of love, integrity, truth, excellence, and relationships, leaders can foster an environment of trust, growth, and long-term success. The true mark of a great leader is making oneself increasingly unnecessary by cultivating broad leadership practice across the team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/370/1*b6jlkC_cPbZb1RhSPHJqFg.gif" /><figcaption>The Office Party Hard GIF</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b7673131e162" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Stay Healthy While Working]]></title>
            <link>https://medium.com/@jgunnison/how-to-stay-healthy-while-working-1b3e5202b3f4?source=rss-be7b38c8ce66------2</link>
            <guid isPermaLink="false">https://medium.com/p/1b3e5202b3f4</guid>
            <category><![CDATA[office-health]]></category>
            <category><![CDATA[habits]]></category>
            <category><![CDATA[office-furniture]]></category>
            <category><![CDATA[work-from-home]]></category>
            <category><![CDATA[health]]></category>
            <dc:creator><![CDATA[Jon Gunnison]]></dc:creator>
            <pubDate>Mon, 22 Jul 2024 17:15:21 GMT</pubDate>
            <atom:updated>2024-07-22T17:15:21.282Z</atom:updated>
            <content:encoded><![CDATA[<p>Switching between sitting and standing and taking regular eye breaks can transform your workday from sluggish to energized.</p><h4>Sitting Is the New Smoking? Let’s Stand Up to That!</h4><p>Sitting for long periods is as bad for you as smoking? Dr. <a href="https://www.startstanding.org/sitting-new-smoking/">James Levine from the Mayo Clinic says, “Sitting is the new smoking.”</a> But fear not! Standing up can save the day. Switching between sitting and standing can improve your posture, boost your energy, and even make you happier.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*n_wiE2_fUz9nRNZqlQr2yw.gif" /></figure><h4>Taking Breaks to Save Your Vision</h4><p>Prolonged screen time leads to digital eye strain, causing dry eyes, blurred vision, and headaches. <a href="https://time.com/4789208/screens-computer-eye-strain/">Dr. Joshua Dunaief from the University of Pennsylvania highlights, “The eyes are not designed to stare at digital screens for long periods. Regular breaks are essential to maintain eye health.”</a></p><p>Enter the 20–20–20 rule: Every 20 minutes, look at something 20 feet away for 20 seconds. This simple trick keeps your eyes happy and healthy. <a href="https://www.neco.edu/about/leadership/about-president-purcell/">Dr. Howard Purcell from the New England College of Optometry</a> says, “Taking regular breaks not only helps to prevent eye strain but also encourages movement and can reduce the risk of developing musculoskeletal issues.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*DvYnEJNYiJZbwBJOilcUjA.gif" /></figure><h4>Practical Tips for a Healthier Workday</h4><p>Making these habits part of your daily routine is easier than you think. Here are some fun tips to get you started:</p><ol><li><strong>Use a Sit-Stand Desk:</strong> Invest in a sit-stand desk or a desktop converter that lets you switch it up throughout the day.</li><li><strong>Set a Timer:</strong> Use a timer or an app to remind you to stand up and move every 30 minutes. Even a brief walk around the office or your home can make a big difference.</li><li><strong>Follow the 20–20–20 Rule:</strong> Give your eyes a break every 20 minutes to look at something 20 feet away for 20 seconds.</li><li><strong>Stretch and Move:</strong> Incorporate stretching exercises into your breaks to relieve muscle tension and improve circulation.</li><li><strong>Stay Hydrated:</strong> Drinking water regularly helps maintain overall health and reminds you to take breaks.</li></ol><h4>Conclusion</h4><p>Switching between sitting and standing and taking regular breaks for your eyes are simple yet powerful strategies to enhance your health and well-being at work. By adopting these practices, you can reduce the risks associated with a sedentary lifestyle and digital eye strain, ultimately leading to a more productive and healthier workday.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1b3e5202b3f4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How We Built and Governed a Design System: A Journey from Conception to Enterprise Adoption]]></title>
            <link>https://medium.com/@jgunnison/how-we-built-and-governed-a-design-system-a-journey-from-conception-to-enterprise-adoption-89d940abee55?source=rss-be7b38c8ce66------2</link>
            <guid isPermaLink="false">https://medium.com/p/89d940abee55</guid>
            <category><![CDATA[enterprise-ui]]></category>
            <category><![CDATA[governancedesign]]></category>
            <category><![CDATA[react-ui-library]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[component-libraries]]></category>
            <dc:creator><![CDATA[Jon Gunnison]]></dc:creator>
            <pubDate>Sun, 23 Jun 2024 23:00:27 GMT</pubDate>
            <atom:updated>2024-06-24T22:01:55.503Z</atom:updated>
            <content:encoded><![CDATA[<p>In the modern world, delivering user-friendly experiences requires both consistency and efficiency. To enhance Allstate’s product user interfaces, we set out to develop a comprehensive and robust design system. As the lead developer, I worked closely with the lead designer to build, scale, and ensure widespread adoption of this system.</p><figure><img alt="My laptop featuring the Allstate Pattern Library Sticker" src="https://cdn-images-1.medium.com/max/1024/1*hwThxLsR2EWOOJLb2WvciQ.png" /></figure><h4>The Evolution of Our Design System</h4><p>Today, Allstate leverages a mature Design System that has been implemented enterprise-wide. This system accelerates time-to-market and ensures consistent user experiences across nearly 100 products developed by Allstate and design vendors.</p><p>The journey began in 2016 when, alongside a lead designer (<a href="https://www.linkedin.com/in/monikawala/">Monika Walankiewicz</a>), we pioneered the company’s first design system. Within a year, we scaled it to support 40 teams. This overview encapsulates the history, current status, and our roles in the creation, operation, and governance of the design system over the years.</p><h4>Governance Strategy and Adoption</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/787/1*S6n6So5GGFN5qcc-j6DEgw.png" /></figure><p>Our most recent endeavor for the Design System was centered around revising the governance strategy and overhauling the contribution model for new patterns for designers and developers.</p><p>In addition, we partnered with the Claims organization to sunset three legacy pattern libraries and adopt the Allstate Design System (ADS) to create consistency with the rest of the enterprise products.</p><h4>Transforming the Design System into a Product</h4><p>In 2021, me and the lead designer played crucial roles in evolving the design system into an independent product supported by its own specialized team. Collaborating with members of the UX Operations team and IBM consulting arm, we crafted a compelling business case that underscored the strategic significance of the design system, outlining staffing and budget needs. This successful effort secured ongoing funding for the project.</p><h4>The Birth of Our Design System</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*lJxC4H8c963M3VR9M3LPog.png" /></figure><p>In overseeing 12 paired designer teams tasked with revamping Allstate agents’ applications, we discovered rampant design inconsistencies. Each team, though well-intentioned, was inadvertently creating variations of the same patterns. It was time to take action.</p><p>Collaborating with the lead designer we adopted an Atomic Design methodology to create a pattern library.</p><h4>How We Did It</h4><p>We organized collaborative sessions with product designers to brainstorm and establish foundational components, laying the groundwork for our design system.</p><p>By establishing a comprehensive design system, we aimed to:</p><ul><li>Eliminate redundancies</li><li>Streamline the design process</li><li>Ensure consistency across all platforms</li><li>Enhance the overall user experience</li><li>Expedite development cycles</li></ul><p>We talked to our users to understand their needs. We treated internal users as if they were customers, conducting in-depth interviews to understand their needs and build a system that’s simple and usable.</p><p>Concurrently, we tackled governance and contribution models. We needed clear guidelines on how designers and developers would contribute to the pattern library.</p><h4>Implementation and Scaling</h4><p>As the foundation developed, the lead designer meticulously crafted these patterns in Sketch, refining color palettes and typography systems, and articulating usage guidelines and design principles. Meanwhile, I spearheaded the development of React components and the establishment of a comprehensive living component documentation site.</p><p>We created two Slack channels for design and development support and established office hours to answer questions and guide the teams in component implementation.</p><h4>Governance and Contribution Models</h4><p>Governance is crucial for maintaining the integrity and consistency of a design system. Our governance strategy included:</p><ul><li>Clear guidelines for pattern contributions</li><li>Regular review sessions to ensure adherence to design principles</li><li>Feedback loops for continuous improvement</li></ul><p>We established a contribution model that allowed designers and developers to propose new patterns and enhancements. These proposals were reviewed by a governance committee to ensure they met the system’s standards.</p><h4>Key Achievements</h4><ul><li><strong>Enterprise Adoption:</strong> The design system was scaled to support nearly 100 products across the enterprise.</li><li><strong>Consistency:</strong> Reduced design-related defects by 25% and accelerated the time-to-market for new features by 20%.</li><li><strong>Efficiency:</strong> Increased development efficiency by 30% through the creation of a centralized design system.</li><li><strong>Quality:</strong> Achieved a 40% reduction in deployment-related issues and a 35% increase in deployment frequency.</li><li><strong>User Satisfaction:</strong> Received positive feedback from users and stakeholders, highlighting the enhanced usability and visual appeal.</li></ul><h4>Conclusion</h4><p>Building and governing a design system is a dynamic process that requires collaboration, strategic planning, and continuous improvement. As the lead developer, I played a crucial role in ensuring the technical robustness and scalability of our system, while the lead designer focused on the visual and user experience aspects. Together, we created a design system that not only meets current needs but is also adaptable for future growth.</p><p>By sharing our journey, we hope to inspire other teams to embark on their own design system projects, leveraging governance strategies to ensure success and sustainability.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=89d940abee55" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Still Not Convinced Progressive Web Apps are the Future?]]></title>
            <link>https://medium.com/@jgunnison/still-not-convinced-progressive-web-apps-are-the-future-30d57e286fba?source=rss-be7b38c8ce66------2</link>
            <guid isPermaLink="false">https://medium.com/p/30d57e286fba</guid>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[web-performance]]></category>
            <category><![CDATA[progressive-web-app]]></category>
            <dc:creator><![CDATA[Jon Gunnison]]></dc:creator>
            <pubDate>Tue, 13 Feb 2018 03:44:19 GMT</pubDate>
            <atom:updated>2018-02-13T03:45:19.105Z</atom:updated>
            <content:encoded><![CDATA[<p>I think for a lot of companies their aware of Progressive Web Apps (PWAs) but their not deploying them as a standard practice. With how incredibly easy they are to implement there’s no excuse to not give your users a fast and reliable experience.</p><p>Maybe it’s just the branding that somehow we think that you need to be developing with a Javascript framework or library to benefit from PWAs but that’s really not the case. Anyone with a website can add manifest.json and a Service Worker. These alone will increase the reliability and performance of your website or web app when configured properly.</p><p>After watching these talks, I believe that it makes the most sense for everyone to start working their way towards PWAs as a default.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FogMjMN1G6V8%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DogMjMN1G6V8&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FogMjMN1G6V8%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/478a9477372f54d3449139b3a2cc5ac4/href">https://medium.com/media/478a9477372f54d3449139b3a2cc5ac4/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FK7ClDLoqxv0%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DK7ClDLoqxv0&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FK7ClDLoqxv0%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/8676cb550e957605f5941f242ca131bb/href">https://medium.com/media/8676cb550e957605f5941f242ca131bb/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F_srJ7eHS3IM%3Fstart%3D1405%26feature%3Doembed%26start%3D1405&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D_srJ7eHS3IM&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F_srJ7eHS3IM%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/44fe76f9cf0e3786cd19603d2036535d/href">https://medium.com/media/44fe76f9cf0e3786cd19603d2036535d/href</a></iframe><p>If your interested in getting started there’s plenty of resources online and I would recommend starting with this recent post from Google Developers.</p><p><a href="https://developers.google.com/web/fundamentals/codelabs/your-first-pwapp/">Your First Progressive Web App | Web Fundamentals | Google Developers</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=30d57e286fba" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Pattern Library Workflow]]></title>
            <link>https://medium.com/@jgunnison/pattern-library-workflow-ba9cc486159e?source=rss-be7b38c8ce66------2</link>
            <guid isPermaLink="false">https://medium.com/p/ba9cc486159e</guid>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[style-guides]]></category>
            <category><![CDATA[pattern-library]]></category>
            <dc:creator><![CDATA[Jon Gunnison]]></dc:creator>
            <pubDate>Thu, 22 Jun 2017 00:00:46 GMT</pubDate>
            <atom:updated>2017-06-28T21:04:06.502Z</atom:updated>
            <content:encoded><![CDATA[<p>Just about a year ago, I started working at Allstate. Myself and my team of two UI Engineers and a Design Lead established a Pattern Library that has been very successful. With the success I decided that it would be a good idea to share our workflow in an article.</p><p>For starters we have the four segments that every Pattern Library is structured with. These start with fundamentals that translate into the coded components and then we bundle together those components into templates. Finally the production ready pages built from the templates and are distributed inside of apps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/690/1*plihRwvkNAmGgSy-stKeQA.png" /><figcaption>Pattern Library Segments</figcaption></figure><ul><li><strong>Fundamentals</strong>: Colors, Iconography, and Typography</li><li><strong>Components</strong>: Buttons, Form Fields, Accordions, etc</li><li><strong>Templates</strong>: Starter Kit and collections of Components</li><li><strong>Pages</strong>: Implementations of the Templates with integration with the backend and the final copy ready for production.</li></ul><p>These segments really help isolate the inner linking dependencies on each-other. Where if we were to update a component we’ll most-likely need to update some templates and so on.</p><h3>The Governance Model</h3><p>Our governance is structured to have different practices branch off but come together as a community for contributions directly to the Pattern Library. The Pattern Library’s Style Guide or Sketch file is maintained and managed by the Designer Librarian role while the Code Base, Deployments, and Bug Tracking is maintained by the UI Developer Librarian role.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/690/1*OOmKuCen24lLCCz47DDsAQ.png" /><figcaption>Governance Community</figcaption></figure><p>The Pattern Library is the source of our tools, our “Life Blood” if you will. The Librarian’s are constantly collaborating on introducing enhancements to the Pattern Library and making the hard decisions when it comes to introducing new Patterns to the library, thus that’s why their called “Librarians”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/690/1*LjTRPHz4ohz0MlFG8mUdcQ.png" /><figcaption>Governance Community Support</figcaption></figure><p>The responsibilities of both Librarian roles aren’t just limited to maintenance and actually have a lot of support and training efforts. Let’s say a team is interested in using the Pattern Library’s resources, they’ll likely need questions answered or on boarding to the resources. The Librarians both work with project teams on that.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/650/1*rPL4p3v60dbPySifLZsmiQ.png" /><figcaption>Typical Design Process</figcaption></figure><p>Our Workflow is similar to any other design process. The “Discover” phase is a collaborative effort between the design teams and the Designer Librarian. They will focus on delivering what’s needed for the project to the Developer Librarian/s. The output of the “Define” phase is to produce the Pattern in the Sketch Style Guide. Once that’s completed the Pattern will go into the “Develop” stage. This is where the Developer Librarian will code and document the Pattern in the Living Style Guide producing something that can be consumed by the project team and others.</p><h3>Establishing Patterns</h3><p>To produce Patterns we use a lot of tools to gather requirements for each Pattern. It usually starts with a designer reaching out to the Designer Librarian on the dedicated Pattern Library Design Slack channel with a need for a new Pattern. It will also come from designers directly where they create a new design and then submit it as a future Pattern in Trello or Slack. The last place we get them is from unmet needs from the developers on project teams. They’ll submit a request into the Github Issues instance for the Pattern Library source code.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/690/1*X3iN6UIsx0L3XXnP7R0TvQ.png" /></figure><p>Once everything is centralized to the Sketch Style Guide it will get deployed out to Zeplin, Invision, and for designers the Pattern Library document where they can download the Sketch file to start using in their own projects.</p><p>After we have the design we stage them with our internal stages.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/690/1*gLEMBUZfrzOEyqVzzdsxLw.png" /><figcaption>Pattern Production Stages</figcaption></figure><ul><li><strong>Snowflake:</strong> A single instance of a component or design that isn’t recognized as a Pattern for the foreseeable future.</li><li><strong>Submitted Design:</strong> A design that has been recognized as a future Pattern</li><li><strong>Refinement:</strong> The stage that the creator/inventor of the Pattern will participate in with the Designer Librarian to add any missing requirements and match up with the fundamentals of the Pattern Library.</li><li><strong>Pattern: </strong>The stage where the design has become a Pattern and can start being developed into code if it hasn’t already started.</li></ul><p>Snowflakes won’t always stay snowflakes and we regularly keep a list of all instances so when we produce a new Pattern or have a business need where that Snowflake could help we’ll start the Pattern process on that Snowflake. Once that process is complete we’ll take the Pattern and go back to any teams that could use it and remediate the existing Snowflakes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/690/1*njSYuoUaes69pnpW-FUgBw.png" /><figcaption>Snowflake Remediation Stages</figcaption></figure><h3>Code Features and Bugs</h3><p>For the development it’s a lot more straight forward. The Developer Librarian will collect the new Patterns from the Sketch Style Guide and add them to the Pattern Library through a Github Issues backlog. The Librarian will also get requests to resolve bugs from project developers in the Github Issues backlog and through the Pattern Library Developer Slack channel which will be prioritized and addressed in the Pattern Library.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/690/1*eKoFGcydJ9quRkmC8IfTzg.png" /><figcaption>Pattern Library Development Process</figcaption></figure><p>The Patterns are then all deployed out to developers through a Node Packages where they can update their projects to the latest version and start using them.</p><h3>Pattern Library Deployment Process</h3><p>The code for the Pattern Library is all hosted on a Github Enterprise repository that holds a Github Issues backlog. That backlog is broken down into semantically versioned release names using Github’s milestones.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/690/1*vMZ8Ial0WUmHhDHVgpOKpg.png" /><figcaption>Pattern Library Deployment Process</figcaption></figure><p>Once a milestone is reach by the end of the week it it will be consumed by Jenkins. Jenkins will build the code and deploy it out to a private Node Package registry called Artifactory. It will also deploy the document site on to our host Cloud Foundry.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/690/1*cGDLOukbWunL_7i03u0YhQ.png" /><figcaption>Consumption Options</figcaption></figure><p>The code can then be consumed through all different sets of tools including NPM (Node Package Manager), Yarn, and Javascript by just including it into a projects HTML script tag. The favored route is to install the package to a project using NPM through Artifactory.</p><p>The coded Patterns are produced using Facebook’s React library and are components that can be consumed by our other projects using React. It’s also important to note that we break out our SVGs into a separate Node Package called “Icon Library” because it’s a lot easier to have them isolated then in the same Package.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/690/1*qGth1GHDP2rRCaH5ZHJsCA.png" /><figcaption>Packages Consumed by Each Project</figcaption></figure><p>Additionally we internally consume the coded Patterns identically to the way our developers do in the Pattern Library Living Style Guide to prevent any issues where our Patterns would work in our instance but not theres. We achieve this by maintaining them as isolated projects within the Github repository but consume them as symbolic links instead of through the registry for development.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/690/1*57sRwq0zeGeDBmSlqNS3Qg.png" /><figcaption>Pattern Library Living Style Guide with Packages</figcaption></figure><p>For a detailed look at the way we have this working here are all of the technologies we have to build our Node Packages.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/690/1*njaaRRlYXoj8fB9k7kZE1A.png" /><figcaption>Detailed Pattern Library Build Process</figcaption></figure><p>The Pattern Library Living Style Guide is also a React project and uses Webpack to build all of the documentation for deployment.</p><h3>Going Further</h3><p>With the experience that we’ve gotten within the year it makes sense to us to expand our governance model to include a coach role. These designers and developers will contribute their time for support and being a voice for the Pattern Library initiatives. They can help with refinement of Patterns, Snowflake remediation, or help with the issues developers might have integrating the Pattern Library code into their projects.</p><p>Additionally I’m really interested in producing Patterns for multiple frameworks such as AngularJS while also theming the coded Patterns so that they can be more versatile.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/690/1*NNfuwEJWbte2PER6hTpKUw.png" /></figure><p>It takes a lot to be a Librarian for a Pattern Library and some would call us Unicorns. Unfortunately Unicorns don’t exist, but Narwhals do.</p><p>If you’d like to read more about this project <a href="https://medium.com/@jgunnison/experiences-developing-a-pattern-library-46c5a0e8067e">I wrote another article going over the process of setting the Pattern Library up</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ba9cc486159e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Experiences Developing a Pattern Library]]></title>
            <link>https://medium.com/@jgunnison/experiences-developing-a-pattern-library-46c5a0e8067e?source=rss-be7b38c8ce66------2</link>
            <guid isPermaLink="false">https://medium.com/p/46c5a0e8067e</guid>
            <category><![CDATA[style-guides]]></category>
            <category><![CDATA[pattern-library]]></category>
            <category><![CDATA[governance-and-tech]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[Jon Gunnison]]></dc:creator>
            <pubDate>Tue, 13 Jun 2017 04:35:24 GMT</pubDate>
            <atom:updated>2017-06-21T23:45:49.397Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tzEr5eOVaQ5sw8Q4QXrO2A.jpeg" /><figcaption>Pattern Library Sticker</figcaption></figure><p>Just about a year ago I joined Allstate and was given the task of assembling a way for developers to collaborate and share code. After a few conversations and some digging through the source code it was understood that the development being produced couldn’t easily be used project to project because of it’s loose standards and narrow implementation.</p><p>On my second week I decided that the best strategy was to establish a Pattern Library with my colleagues by using what existed but refining it into reusable components. Centralized to me was a team of two UI Engineers and a Design Lead, which is small but could accomplish the task.</p><p>Together we spent our first few weeks dedicated to putting together the Pattern Library’s living style guide codebase, gathering requirements from existing designs, and establishing nomenclature with all of the designers in two workshops. Once names were established for every component we started to add them into a living style guide and a Sketch document allowing us to start building out components.</p><p>The cadence we decided on was to release weekly Node Packages from the code base, update the Pattern Library site, distribute the new Sketch Style Guide, and document the new designs from the Sketch document into a Github Issues backlog every Friday. Starting Monday every product team could update their codebase with the new updates and we could start working on the Github Issues backlog for that upcoming Friday.</p><p>We also built the Pattern Library with an <a href="https://www.oreilly.com/ideas/getting-started-with-innersource">InnerSource</a> model in mind and allowed for everyone to contribute code, submit bugs, and request new features.</p><p>Some of the challenges we faced through-out the year specifically pertained to the following.</p><ul><li>In the first couple months we had growing pains with developers adopting the code but not having enough from it to build something useful.</li><li>Setting the standards and expectations for our team so that we’re helping communicate what’s needed to be in the documentation and included in the code.</li><li>Setting expectations with the developers and designers on the product teams so that they could know when to expect their contributions in a release.</li><li>Developing a governance model that would allow for remediation of larger collections of components in the developed products.</li></ul><p>We resolved our growing pains by prioritizing better with the teams so that we could deliver what they needed when they needed it. This also helped resolve the expectations we were missing with our product teams as well. Our standards took a short while but we had a few conversations and documented them and it wasn’t to terribly hard to get everyone on the same page. The governance model is something we’re constantly working and hope to get it a less iterative state but it’s a lot like the Agile methodology and how you’re constantly improving on it.</p><p>With all of this it’s been very successful and we’ve gotten more than twenty development teams using it today and more on their way. It’s truly been a thrilling ride and we have plans to grow further from here.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=46c5a0e8067e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Prototyping Design to Production Workflow]]></title>
            <link>https://medium.com/@jgunnison/prototyping-design-to-production-workflow-678b42da7b7c?source=rss-be7b38c8ce66------2</link>
            <guid isPermaLink="false">https://medium.com/p/678b42da7b7c</guid>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[process]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Jon Gunnison]]></dc:creator>
            <pubDate>Mon, 12 Jun 2017 04:56:14 GMT</pubDate>
            <atom:updated>2017-06-12T04:56:14.083Z</atom:updated>
            <content:encoded><![CDATA[<p>For starters, let’s take a look at the typical process that most teams work under. This doesn’t matter if you’re waterfall or some form of agile, you probably have a structure like this for getting your projects onto the web.</p><h3>The Typical Process</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O-zziUzzjbtn2l4IBABxKg.jpeg" /><figcaption>The Typical Process</figcaption></figure><p>Phase one involves discovery:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lSUtehOw2ZuzEhDsn9yxSw.jpeg" /></figure><p>Phase two is where you produce your designs:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r9tTg7-P_xcjUvl1M4kJ3Q.jpeg" /></figure><p>Phase three is the development from the designs:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rAdU1p2elFnwUh-A5U55tw.jpeg" /></figure><p>Then two weeks or a month plus later deployment can happen.</p><p>In my experience anytime that I’ve seen this process at play it almost always needs to circle back to the beginning due to bad deliverables. Specifically a set of bad deliverables that has trouble communicating complex interactions and desired outcomes. And if done extremely poorly this can result in reset of the processes second and third phases of additional effort to correct.</p><p>A lot of problems come with the handoff process of the first and second phase deliverables being static. These include wireframes and mockups and here are just a few issues I see with them.</p><p>Wireframes:</p><ul><li>Describing interactions on a static deliverable involves a lot of conjecture and effort</li><li>Can result in teams feeling like they have to do what is outlined, no matter what is discovered later</li><li>Revisions ultimately needed when too many discoveries drastically change the original vision</li></ul><p>Mockups:</p><ul><li>Pixel perfect detail can be duplicative work, when communicating already-standardized design patterns</li><li>Can get stakeholders focused on minor visual details rather than the bigger picture too early in the process</li><li>Identical revision issues as wireframes, depending on which type of deliverable the organization is looking for at that time</li></ul><p>We create static wireframes to communicate structure and the user interface requirements for customer needs and behaviors. And we create mockups to communicate aesthetics.</p><p>Here’s one way to prevent this. Depending on the use case, front-end code may take less time to produce than a wireframe and/or a high-fidelity comp and can be started right at the beginning of discovery. These are normally called prototypes and they maximize the efficiency of delivering products.</p><p>Straight from paper sketches to production ready interactive simulations when testing. Here are some of the benefits I’ve seen from working this way.</p><ul><li>Helps teams experiment with multiple approaches and ideas</li><li>Facilitates discussion through visuals instead of words</li><li>Ensures that everyone shares a common understanding</li><li>Reduces risk and avoids missed requirements</li></ul><p>Additionally they also offer a lot of cost savings because with the ‘typical process’ you’re spending time and money on every deliverable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MkSP6XnhSyUpHhEZz6_UzA.png" /></figure><p>Here’s how this process looks after reorganizing the workflow:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gbP_iQCW3eb2-9YH3Y2leg.png" /></figure><p>You’ll also have some shifted roles for each discipline and once a pattern and its requirements have been validated they can be reused and refined, Reducing bloat and decreasing the time spent on correcting inconsistencies. Instead of focusing on pages. Focusing Wireframes and Mockups on patterns and components like buttons, headings, links, and search bars breaks down everything into reusable pieces that can be coded and reused everywhere, not just once.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YGYF5ZrU3VoWnqoI4V0LbQ.png" /></figure><p>This can all be easily produced so that everyone can use these patterns and components without interruptions.</p><p>As a bonus it drives consistency and enforces a stronger nomenclature for focused discussions.</p><p>The benefits you can potentially see from this process is:</p><ul><li>Strong focus on content and functionality</li><li>Improved communication surrounding projects</li><li>Reusable code and patterns</li><li>Minimal waste to produce final product</li><li>Maximize efficiency in delivering products</li><li>Incorporate technological and design needs for responsive and adaptive frameworks from day one</li><li>Deliverables become tools to drive conversations, not to lock teams into final solutions</li></ul><p>The difficulty with getting this off the ground is the availability and knowledge of Front-End development in your organization. With that said it’s ideal to have designers that know basic HTML and CSS and can contribute to the production Front-End code. Of course if not it’s ideal to experiment first with the low cost “paper prototypes” and then move forward with Front-End development and perhaps even pairing a designer with a developer to produce the project.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=678b42da7b7c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My First Pattern Library (Experiences in Web Development)]]></title>
            <link>https://medium.com/@jgunnison/my-first-pattern-library-experiences-in-web-development-c1302eaea2d7?source=rss-be7b38c8ce66------2</link>
            <guid isPermaLink="false">https://medium.com/p/c1302eaea2d7</guid>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[style-guides]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[storyofmylife]]></category>
            <category><![CDATA[pattern-library]]></category>
            <dc:creator><![CDATA[Jon Gunnison]]></dc:creator>
            <pubDate>Mon, 12 Jun 2017 04:45:04 GMT</pubDate>
            <atom:updated>2017-06-12T04:45:04.781Z</atom:updated>
            <content:encoded><![CDATA[<p>Back when I started work at Paylocity I was a Front-End Developer for the larger set of product teams. All of their developers at the time were DotNet focused and they needed people like me to produce their client-side code (HTML, CSS, JavaScript). Specifically my job was to work with Interaction Designers and Product Managers to produce production Front-End code for each of the 12 large products. I was personally assigned to two in the beginning that they wanted to refactor visually.</p><p>There was an initiative to start developing reusable code components but it never really picked up due to it being a secondary priority. With that need being a lot that held us back I personally took on putting together a basic style guide using Wordpress and I used my third assigned project to produce all of the components we started to need. The worst part of starting it was that the design had no style guide to look to in order to create UX/UI consistency so a lot was working with designers to get specifications on colors, icons, and brand guidelines.</p><p>Once we collectively had enough to start promoting it to teams so that they could consume it we starting to think of a name for it. The name we decided on was Citrus.</p><p>Citrus was a successful and it started to reform the design teams approach to work. We then rebranded to the UX team and instead of producing full code for the development teams, we started educating the teams and supporting them from our centralized team of Designers, Information Architects, and Front-End Developers. Citrus still is, the official Style Guide of Paylocity and it efficiently and effectively communicates many things, including</p><ul><li>Brand Identity (for Marketing)</li><li>Coding Standards (for Development)</li><li>Coded Design Components (for Cross-Functional Teams)</li></ul><p>And simultaneously acts as a central repository for the UX team to deliver and promote cohesive standards to all of the product development teams.</p><p>I’m glad I was apart of that transformation and I’m glad to know that it’s started a new era at Paylocity.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c1302eaea2d7" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>