<?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 Red Badger on Medium]]></title>
        <description><![CDATA[Stories by Red Badger on Medium]]></description>
        <link>https://medium.com/@redbadgerteam?source=rss-2cc5610543dc------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*6rkXfPPqIjZavlEN6v1C-w.jpeg</url>
            <title>Stories by Red Badger on Medium</title>
            <link>https://medium.com/@redbadgerteam?source=rss-2cc5610543dc------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 04:09:46 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@redbadgerteam/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[Got a gender pay gap? It’s hurting your business.]]></title>
            <link>https://medium.com/red-badger-thinks/got-a-gender-pay-gap-its-hurting-your-business-7f97bb5c8f9b?source=rss-2cc5610543dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/7f97bb5c8f9b</guid>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[diversity]]></category>
            <category><![CDATA[collective-intelligence]]></category>
            <category><![CDATA[diversity-and-inclusion]]></category>
            <category><![CDATA[gender-equality]]></category>
            <dc:creator><![CDATA[Red Badger]]></dc:creator>
            <pubDate>Mon, 04 Nov 2019 16:01:04 GMT</pubDate>
            <atom:updated>2019-11-04T16:01:04.100Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QAxG_m_9m0SAdw_YkeKlLA.png" /></figure><p><strong>Fix it and feel the benefits.</strong></p><p>Closing the gender pay gap isn’t just the right thing to do, it makes perfect business sense too.</p><p>In this article, I dive into the surprising factors behind the gap (spoiler: personality has a huge impact), share what you can do to fix it (with actionable steps based on Red Badger learnings), and outline the benefits you’ll unlock (productivity, creativity, and more).</p><h3>What’s the size and shape of the gap?</h3><h3>Let’s dive into the data</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*uVxauW89RZ5WhLIH" /></figure><p>According to the Government Equalities Office’s <a href="https://assets.publishing.service.gov.uk/government/uploads/system/uploads/attachment_data/file/819665/Mandatory_Gender_Pay_Gap_Reporting_Summary_of_reported_data_for_2018-19.pdf">Mandatory Gender Pay Gap Reporting</a> for 2018/1⁹¹, of 10,814 companies and public bodies in Britain, 78% of reported median gender pay gaps favoured men compared to 14% that favoured women. 9% of employers reported a median gender pay gap of exactly 0%.</p><p>88% of the companies reported a mean gender pay gap that favoured men, with 11% favouring women. 1% of employers reported a mean gender pay gap of exactly 0%.</p><p>Of the 9,583 companies who reported in both 2017/18 and 2018/19, 48% of them reported a median gender pay gap that narrowed over the 12 month period. 44% reported that it had widened.</p><p>So what do the numbers mean? The figures show little improvement year on year. This could be down to complexity, with changes taking time to show up in the stats. But it’s also been reported that companies are seriously struggling to know how to make positive change. On top of that, other countries’ data also reveals this is a global issue.</p><p>NOTE: Take a look at <a href="https://www.theguardian.com/society/2019/feb/28/what-is-gender-pay-gap-reporting-and-what-does-it-mean">this article</a> for a definition of median and mean gender pay gaps.</p><h3>Why does the gender pay gap exist?</h3><h3>Some surprising factors are at play.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*BH-OvyQy2kkqhYa2" /></figure><p>All of the empirical data shows that women and men’s average intelligence is <a href="https://www.cambridge.org/core/books/human-intelligence/AD31C363F9C77921A469921B85185278">identical</a>. So, of course, intelligence isn’t behind the gender pay gap. Many other reasons are suggested, including discrimination. But, perhaps surprisingly, <a href="https://www.jstor.org/stable/25067572">studies</a>² have shown that personality has a larger impact. Enter the Five Factor Model of Personality Structure.</p><p>The <a href="https://www.psychologistworld.com/personality/five-factor-model-big-five-personality">Five-Factor Model</a> originated from work in the 1930s, was advanced by researchers Ernest Tupes and Raymond Christal in 1961, and became widely accepted amongst academic audiences in the 80s.</p><p>It breaks personality down into five key components:</p><ul><li>Extroversion vs Introversion</li><li>Agreeableness vs Antagonism</li><li>Conscientiousness vs Lack of Direction</li><li>Neuroticism vs Emotional Stability</li><li>Openness to Experience vs Closedness to Experience</li></ul><p>Studies show that personality predicts earnings for both men and women. For example, in men, a one-standard-deviation increase in non-agreeableness raises the hourly salary of workers by an average of 4%-6%. In comparison, a one-standard-deviation change in IQ for men results in up to a 17% increase in hourly wage. But when you package personality into a bundle of traits, personality has the same impact on men’s pay as cognitive ability.</p><p>When we start to look at the differences between the genders, women are much more likely than men to be agreeable, neurotic, extroverted and open. And it’s agreeableness and neuroticism where we see by far the largest difference.</p><p>When you link that to pay, the overall findings show that 16% of the gender pay gap is due to personality traits versus 13% which comes down to labour market rewards and penalties — discrimination, in other words. So personality has more of an impact on the gender pay gap than discrimination.</p><p>The 16% I just mentioned is driven by one major factor, and that’s agreeableness. Who knew agreeableness could be so problematic? It’s deeply unfair but nevertheless true that people who are friendly, compassionate and altruistic get paid less.</p><p>How does this come to pass? The value ‘agreeable people’ place on interpersonal relationships prevents them from demanding the rewards that create better outcomes for themselves. This impacts women the most as they’re more likely to be agreeable. Meanwhile, men receive rewards for being non-agreeable.</p><p>Why are men rewarded for non-agreeable behaviours? It comes down to labour market sorting, discrimination, and bargaining.</p><p>Let’s take a closer look at all three factors:</p><p><strong>Labour market sorting</strong></p><p>Non-agreeable workers, primarily men, more often select into occupations where being non-agreeable is required and rewarded as a productive trait. This is apparent across many industries, including my industry — technology.</p><p><strong>Discrimination</strong></p><p>The market rewards men and women who conform to traditional gender roles and it punishes those who deviate. Agreeable men and non-agreeable women are punished for being perceived as too feminine and too masculine, respectively. We’ve all heard of the non-agreeable man being classed as ambitious vs the non-agreeable woman being classed as bolshy or bossy. Fortunately for men, they’re much more likely to be non-agreeable and are rewarded accordingly.</p><p><strong>Wage Bargaining</strong></p><p>Non-agreeable personalities result in men tending to be better at salary negotiation. There are multiple studies on this but it’s covered brilliantly in the 2003 book <a href="https://docs.google.com/document/d/1N_ANcOuMBTNhG-wv7PM-QgKMqHS_sRoA6DP0PeayYSI/edit#">Women Don’t Ask: Negotiation and the Gender Divide</a>³. The authors, Babcock and Laschever, argue that women shy away from negotiations and assert that, if women do start negotiating, they tend to ask for less than men do in their opening offer. Women also tend to concede faster. For line managers, it’s easier to say yes when asked. Thus men are more likely to be rewarded with a pay rise. As the saying goes, “Don’t ask, don’t get”.</p><p>Some of the studies I’ve read simply lay out the facts, without gesturing towards possible solutions. Other studies suggest that, in order to secure higher pay, women should consider changing their behaviour to be more assertive — a facet of extroversion. In other words, such studies encourage women to exhibit more ‘masculine’ traits that won’t be penalised by gender stereotypes.</p><p>Women are penalised for being non-agreeable as this is interpreted as a break from the gender norm. However, women can be very successful by being assertive (a trait that belongs to the extroversion group rather than the agreeableness group in the Five Factor Model) if they can <em>regulate</em> their behaviour. The research⁴ shows that women get more promotions when they are able to show ‘masculine’ traits — assertiveness, confidence and aggressiveness — but are also able to be self-aware, switching the traits on and off when needed. Being able to regulate those ‘masculine’ traits makes them even more successful than non-agreeable men.</p><p>Many clinical psychologists provide assertiveness training to women to help their careers. I have a problem with this for three reasons. Firstly, as I’ve already mentioned, women who demonstrate non-agreeable behaviours can, in fact, be penalised for these. They’re labelled bossy, while men are deemed ambitious. (Or, society demands that they do a tonne of behavioural and emotional gymnastics to regulate their non-agreeableness and assertiveness, as we’ve seen.) So, while personality factors play a leading role in creating the gender pay gap, so do culture’s discriminatory assumptions about what a trait means for a woman vs a man.</p><p>Secondly, drives to instil assertiveness in women are bad for the industry as they strip extremely valuable ‘feminine’ behaviours (women score higher in social sensitivity — the ability to accept and perceive others’ thinking, mood, and behaviour) from businesses by encouraging women to exhibit more ‘masculine’ behaviours. This reduces the collective intelligence of teams (more on this in a moment).</p><p>Thirdly, and crucially, it should not be the responsibility of women to change their behaviour. Not all women are going to have access to assertiveness training or even be aware of it. We should talk about the speed of change here, too. Change to a pervasive problem across many industries will be slow, and minimal if the answer is for women to alter their behaviours, one woman at a time.</p><h3>The gap is bad for business.</h3><h3>Leaders need to step up.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*duVtm5IiKO4Bz2PH" /></figure><p>The responsibility lies not with individual women, but with leaders. It’s on them to implement policies that ensure a woman’s level of agreeableness doesn’t correlate to her pay.</p><p>And — to be clear — I’m talking about leaders of all genders. The gender pay gap hurts women the most, but it also impacts everyone. This is not simply a ‘women’s issue’. It’s a collective problem that must be solved collectively. Historically, most male leaders have failed to take note and take action.</p><p>Leaders of all kinds need to step up for two key reasons. Firstly, because it’s the right thing to do. As leaders, we carry ethical and social responsibility. Secondly, eradicating the gender pay gap makes business sense. Why? Because the gap limits — and harms — companies by impacting the bottom line performance of teams and individuals, especially in cognitive, creative and collaborative fields of work.</p><p>Let’s look at the altruistic imperative first. It’s increasingly critical that companies do the right thing when it comes to purpose, ethics and social responsibility. Included in this is fairness regarding equality, diversity and inclusion. And, of course, this is one of the territories in which the gender pay gap sits.</p><p>The tech industry is trending towards more companies being <a href="https://www.businessroundtable.org/business-roundtable-redefines-the-purpose-of-a-corporation-to-promote-an-economy-that-serves-all-americans">purpose-driven</a>. Evidencing this, a recent announcement by the U.S. <a href="https://www.businessroundtable.org/">Business Roundtable</a> aimed to redefine the purpose of a corporation to serve society as a whole, creating value for employees and customers, and taking responsibility for serving the local community, not just creating shareholder value.</p><p>As more young people start their careers, and the competition for talent intensifies, the industry needs — more than ever — to be purposeful and invest in people, rather than simply seeing them as assets. Businesses need to think about how they can elevate everyone’s careers. Treating people fairly and paying them for their value is the right thing to do.</p><p>Social good also makes business sense. Jamie Dimon, Chairman and CEO of JPMorgan Chase &amp; Co. and Chairman of the Business Roundtable says: “Major employers are investing in their workers and communities because they know it is the only way to be successful over the long term.” This move isn’t because CEOs of the largest corporations have suddenly grown a conscience. They are fully aware that purpose, ethics and social responsibility are vital to attracting today’s younger talent as these aspects have become much more important to the younger generations.</p><p>Doing the right thing will fuel your business’s performance. In order to improve the efficacy of your company, teams, and individual employees, you need to unlock employee potential, creativity and motivation. When it comes to teams, collective intelligence is a significant factor. And when it comes to individuals, personal motivation counts.</p><p><strong>Collective Intelligence</strong></p><p>Anita Wooley, Associate Professor of Organizational Behavior at Carnegie Mellon, has proven that having diverse teams in which multiple genders and cultures are represented is more important than intelligence when it comes to improving productivity and creativity. These findings are presented in her seminal 2010 work <a href="https://science.sciencemag.org/content/330/6004/686">Evidence for a Collective Intelligence Factor in the Performance of Human Groups.</a>⁵ Wooley names this phenomenon ‘collective intelligence’ (the ‘c-factor’) and differentiates it from general intelligence (the ‘g-factor’).</p><p>Wooley’s 2010 paper, and subsequent studies prove that by doing a group version of an IQ test, you can predict how teams will perform in the future. Having more women than men in a team (but not exclusively women) results in a higher c-factor, as does ethnic diversity and cognitive diversity.</p><p>Teams cannot achieve their highest levels of collective intelligence unless they have at least moderate diversity across all of these factors. Teams comprised of diverse employees provide the best results.</p><p><strong>Personal motivation</strong></p><p>When it comes to the individual, you have to look at what personally motivates your employees. In his famous book <a href="https://www.amazon.co.uk/Drive-Daniel-H-Pink/dp/184767769X">Drive</a>, Dan Pink proves that pay and bonuses that are tied to personal performance have a negative impact on motivation for those in cognitive or creative jobs. Extrinsic motivators just don’t work.</p><p>Instead, you have to focus on <em>intrinsic</em> motivators. The key three are autonomy, mastery and purpose. However, for intrinsic motivators to work, you have to take money off of the table. The intrinsic motivators only work if people feel they are paid fairly. If they feel like they’re paid unfairly, then providing them with autonomy, mastery and purpose is futile.</p><p>It pays to loop personality back into the equation here. If you value the quality of asking for a pay rise and don’t give pay rises to those that don’t ask, you’re at risk of discriminating against women because women are more likely to be agreeable.</p><p>This could result in your company having a large percentage of your very talented (female) employees feeling like they’re paid unfairly, thus being less motivated and doing poorer work than they’re capable of. So even if you don’t care about doing the right thing (which you should) not having policies in place to counter agreeableness being a factor in people’s pay will hit the quality of your company’s output. And that’ll take its toll on your revenue and profit.</p><p>It makes good business sense to set your company up to do the right thing, be purpose-driven, treat all employees fairly and have equal opportunities for all. An important part of this is to have policies in place around pay that allow you to attract and motivate a diverse group of employees, so you can improve your company’s performance and bottom line.</p><h3>Change is possible.</h3><h3>Here’s what you do.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*C6sohS-Qfi1ttrq6" /></figure><p>This is Red Badger’s gender pay gap data. We’ve still got work to do to get these numbers down to zero, but our figures are industry-leading.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*d9N01Om-LOIZh1bC" /></figure><p>As I’ve learned, there’s a lot you can do to ensure you’re paying people fairly and are avoiding a large gender pay gap.</p><p>Here are four tips to get you started:</p><p><strong>Break down gender stereotypes around childcare</strong></p><p>Women’s careers are often halted when they become mothers. This can impact their whole career. For many women, this even <a href="https://doi.org/10.1787/pension_glance-2015-6-en">impacts the amount of pension</a> that they get to draw when they retire.⁶</p><p>To counter this, parental leave should be genderless. Give employees the option to share time off between two primary caregivers after the birth of their baby or adoption of a child. Regardless of their gender, sexual orientation, age, ethnicity, or other characteristics, you should entitle them to take out enhanced parental leave at any time within the first year of their baby’s life or within the first year after adoption.</p><p>A shift in mindset is needed. ‘Time off’ on maternity or paternity leave should be seen as a key part of an individual’s development. Put policies in place for both men and women away on parental leave to be included in any pay reviews. After all, they’ll have picked up and developed a whole host of new, valuable skills during this period.</p><p><strong>Make sure your leadership is balanced</strong></p><p>To close your gender pay gap, you need a balanced leadership team. Evidence shows that having an evenly balanced gender split at leadership level will help ensure your gender pay gap is tackled effectively.</p><p>Unbalanced leadership is a pervasive issue across the industry. In 2018, there were more <a href="https://www.independent.co.uk/news/business/news/women-ftse-100-gender-discrimination-pay-gap-board-representation-chief-executive-a8244361.html">Chief Executives called Dave</a> in charge of FTSE 100 companies than there were women. There were nine Daves, seven women, five people from ethnic minority backgrounds, and four Steves. You don’t have to be a statistician to see that when you add the Daves and Steves together they outnumber the sum of women and people from ethnic minority backgrounds. It’s laughable but not funny.</p><p>NOTE: Take a closer look at this data in <a href="https://www.theguardian.com/news/ng-interactive/2018/apr/05/women-are-paid-less-than-men-heres-how-to-fix-it">The Guardian</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*16bg190t2CcyvPW7" /></figure><p>The article states: “The Guardian analysis of the data shows that in companies where women are fairly or slightly overrepresented in the top pay band, the median gender pay gap shrinks relative to the composition of the company as a whole.”</p><p>If either gender is overrepresented in leadership, the average outcome is that it favours that gender regarding pay. So a healthy balance at leadership is key.</p><p><strong>Be transparent about pay</strong></p><p>Ensure that salary bands, role definitions and expectations of each role at each level are clearly publicised. You want to give employees the opportunity to interrogate and challenge where they sit in the salary bands within the context of what is expected of them and the value they bring.</p><p>At all times, you as a company also want to be able to justify where someone sits and the value they bring. You should be comfortable about having honest conversations and invite debate with any employee about the value they contribute and their corresponding pay. As research professor Brené Brown asserts: “Clear is kind. Unclear is unkind.”⁷</p><p><strong>Continuously audit your processes</strong></p><p>If you want to stop agreeableness being a factor in people’s pay, you need to continuously audit the processes through which pay rises are requested and rewarded. As part of this, you need to ensure that a pay rise can’t be issued by just one person.</p><p>When software engineers write code we make sure the developer who wrote the code cannot also merge it. This supports quality. You must have a code review. To ensure pay is fair, you should follow a similar process. This will help ensure emotion is removed from decisions as far as possible and, instead, encourage decision-makers to focus in on the value of the employee.</p><p>At Red Badger, we have an annual pay review system. It’s split into three stages:</p><ol><li><strong>External benchmarking</strong>: We make sure our salary bands are consistent with the market.</li><li><strong>Pay rise recommendations</strong>: Managers put forward their recommended pay rises for each employee.</li><li><strong>Calibration</strong>: All the recommended pay rises, from across all departments, are reviewed by multiple heads of department.</li></ol><p>The third and final step is the most important. We want to avoid a person being paid a certain amount because one leader is more generous than another. So, as a group, the reviewers calibrate what’s fair across the full cohort of employees. Any pay rises outside of the annual pay review (such as via a promotion) get the same treatment.</p><p>Consistency is key to ensuring fairness. It’s important to have someone who attends all of the calibration meetings, to ensure what’s discussed is consistent and all employees are paid fairly.</p><p>Standing your ground helps to drive fairness, too. If someone who’s currently paid fairly insists on a pay rise, review their request. But be prepared to reject their request and refuse to budge, even if they threaten to leave. You don’t want to put a worth on personality traits (yep, you’ve guessed it — non-agreeable ones) that reward people asking for a pay rise.</p><p>And all this doesn’t demand you to be stingy. Rather, you should focus on being proactive in making sure everyone is always paid fairly.</p><h3>It’s not easy.</h3><h3>But it’s worth it.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ceFdeuPrgjskEmhc" /></figure><p>Some of these initiatives might sound cumbersome, or even counter-productive. But they work. It’s a lot of effort, but it’s totally worth it to ensure people are paid their value.</p><p>If you successfully implement what I’ve outlined, the results will speak for themselves.</p><p>You’ll unlock:</p><ul><li>An ingrained culture of fairness</li><li>Pay that’s free from discrimination</li><li>Pay that’s not impacted by agreeable or non-agreeable character traits</li></ul><p>Pay should not be at the forefront of your employees’ minds. Everyone should be happy and impressed that they’re paid fairly, with pay therefore ceasing to be an everyday issue. Once you’ve achieved this ‘brilliant basic’, you can focus on building diverse teams, giving them intrinsic motivators to get excited about, and providing them with a great environment in which to work and grow.</p><p>Ultimately, the gender pay gap exists because historically business has been run by a patriarchal leadership that’s evolved behaviours which reward men more than women. All of the evidence and data shows that it’s time for a change.</p><p>If every company develops meaningful policies around equality, diversity and inclusion and eradicates their gender pay gap, our businesses will be healthier, our teams will do better work, our talent pool will flourish, and our industry will be stronger. Are you in?</p><p><strong>References</strong></p><ol><li>Government Equalities Office’s — <a href="https://assets.publishing.service.gov.uk/government/uploads/system/uploads/attachment_data/file/819665/Mandatory_Gender_Pay_Gap_Reporting_Summary_of_reported_data_for_2018-19.pdf">Mandatory Gender Pay Gap Reporting</a></li><li>Mueller, Gerrit, and Erik Plug. “<a href="http://www.jstor.org/stable/25067572">Estimating the Effect of Personality on Male and Female Earnings.</a>” Industrial and Labor Relations Review, 2006, vol. 60, no. 1, pp. 3–22.</li><li>Linda Babcock and Sara Laschevar “<a href="http://www.jstor.org/stable/j.ctt7rh37">Women Don’t Ask: Negotiation and the Gender Divide.</a>” 2003, STU — Student edition ed., Princeton University Press</li><li>Olivia A. O’Neill, Charles A. O’Reilly III — <a href="https://onlinelibrary.wiley.com/doi/abs/10.1111/j.2044-8325.2010.02008.x">Reducing the backlash effect: Self‐monitoring and women’s promotions</a> — Journal of Occupational and Organisational Psychology — December 2011, Volume 84, Issue 4, pp. 825–832</li><li>Anita Williams Woolley, Christopher F. Chabris, Alex Pentland, Nada Hashmi, Thomas W. Malone — <a href="https://science.sciencemag.org/content/330/6004/686">Evidence for a Collective Intelligence Factor in the Performance of Human Groups</a> — Science, 29 Oct 2010: Vol. 330, Issue 6004, pp. 686–688</li><li>OECD — <a href="https://doi.org/10.1787/pension_glance-2015-6-en">Pensions at a Glance 2015</a></li><li>Brené Brown, “<a href="https://www.penguinrandomhouse.com/books/557595/dare-to-lead-by-brene-brown-phd-lmsw/">Dare to Lead</a>.” 2018, Random House</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7f97bb5c8f9b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/red-badger-thinks/got-a-gender-pay-gap-its-hurting-your-business-7f97bb5c8f9b">Got a gender pay gap? It’s hurting your business.</a> was originally published in <a href="https://medium.com/red-badger-thinks">Red Badger thinks</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Innovation (without the) Lab]]></title>
            <link>https://medium.com/red-badger-thinks/innovation-without-the-lab-4ca90669a03?source=rss-2cc5610543dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/4ca90669a03</guid>
            <category><![CDATA[experiment]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-strategy]]></category>
            <dc:creator><![CDATA[Red Badger]]></dc:creator>
            <pubDate>Mon, 07 Oct 2019 08:08:59 GMT</pubDate>
            <atom:updated>2019-10-07T08:08:59.438Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="An illustration of stickmen destroying a chemistry lab" src="https://cdn-images-1.medium.com/max/1024/1*NRAA8HBlMU50MkX9bEHKTA.jpeg" /></figure><p>Despite up to <a href="https://www.ideatovalue.com/inno/nickskillicorn/2017/07/15-most-important-innovation-theories-your-company-should-be-using/">96% of all innovation projects failing to make any return on investment</a> and 97% of large businesses believing digital innovation to be <a href="https://www.accenture.com/us-en/_acnmedia/Accenture/next-gen/B20/Accenture-DCI-Report-Final.pdf">critical to their future success</a>, how do organisations find the balance between challenging the status quo and creating innovative products and services time and time again?</p><p>Generally speaking, organisations have 3 options when starting out on their innovation journey — build, partner or buy.</p><p>There are trade-offs associated with each option;</p><ul><li><strong>Partnership</strong> — offers the shortest time to market, limited impact on internal resources and provides the lowest switching cost. However, this comes at a price — quite literally. Partnerships offer the least control, increased integration costs and are likely to offer the lowest margins as any profits are usually shared.</li><li><strong>Buy</strong> — Buying a competitor (or innovative start-up) allows relatively short time to market and any intellectual property (IP) becomes their own. However, this usually comes with significant acquisition costs and a non-trivial integration headache.</li><li><strong>Build</strong> — Generally the most favoured approach (and focus for this blog). Enables internal capability, IP is proprietary and offers the most profitable option. However, it comes with high set up &amp; switching costs and usually results in a longer time to market timeframes.</li></ul><p>However, organisations often fail to build successful internal innovation functions. They usually have neither the depth of in-house expertise, understanding of how to set one up, or are not structured appropriately to facilitate repeatable innovation.</p><p>Innovation Labs are just one example of how companies have sought to build internal innovation capability. Often touted as the silver bullet to the innovation dilemma; Labs are internal (but independent), free from the bureaucracy and constraints of the legacy business.</p><p>However, in reality, Labs also fail to deliver innovative products and services businesses are so desperately seeking. They can become siloed, lack alignment with the organisation’s strategic goals, or lack the appropriate funding models.</p><p>Vast amounts of money can be sunk into ‘innovation’ programs which result in limited numbers of successful innovations ever seeing the light of day. It’s often hard to demonstrate return on investment and Labs often get shut down entirely being regarded as a failure.</p><p>Many suffer from an even worse fate; a term Steve Blank calls ‘innovation theatre’ — where a company shows people that ‘innovation’ is happening, but none of which results in tangible outcomes.</p><p>So, whether you’re searching for the next £100m business idea, you want to dodge disruptors, develop new products and services or are simply trying to progressively transform a legacy platform, the reality is that if you’ve set up an Innovation Lab, it may not be the right approach.</p><p><strong>You don’t need a Lab</strong></p><p>Innovating successfully within a corporate environment requires a laser-sharp focus and a significant shift in mindset — something that doesn’t necessarily come easily in traditional corporate environments.</p><p>A culture of innovation needs to permeate throughout the organisation and needs to be driven from the top down. The C-Suite needs to create a framework that embraces and encourages innovation, no matter where it comes from. They are responsible for ensuring strategic alignment between the business and innovation, but they also need to be prepared to invest in propositions that may cannibalise the core of the company’s business model.</p><p>The following outlines some key factors to consider when planning a successful innovation function.</p><p><strong>Territory definition and its proximity to core</strong></p><p>It’s critical to understand your organisations’ innovation objectives. Are they looking for new products &amp; services to maintain/defend an existing business model? Are they looking to build new value propositions in adjacent markets? Or do they want to build completely new businesses?</p><p>Understanding this will help to align business outcomes with the strategic goals of your organisation. It will also help you shape what metrics you should track — more on that later.</p><p><strong>Innovating in the open with small cross-functional teams</strong></p><p>Much has been written about <a href="https://www.forbes.com/sites/henrychesbrough/2011/03/21/everything-you-need-to-know-about-open-innovation/#3f1b8c3375f4">Open Innovation</a>, but the concept of decentralising innovation makes the process collaborative and far more likely to succeed. Labs can’t innovate effectively within a silo. Innovating in the open drives collaboration throughout the business.</p><p>Embed small teams of 2–3 people throughout the organisation whose sole job is to focus on experimentation to validate new ideas. Small teams with access to subject matter experts will help keep the team focused and nimble. As they work closely with the business, ideas are likely to be grounded in reality and far more likely to succeed.</p><p>Traditionally, there are teams/departments that inadvertently stifle innovation (marketing, brand, legal to name just a few). Part of their job is to be risk-averse — protecting brand reputation, minimising legal litigation etc. By engaging such teams from the outset will significantly increase the likelihood of success. They may even be encouraged to innovate, get out of the building and talk to customers themselves, which can only be a good thing.</p><p><strong>Industrialised experimentation and proof of life</strong></p><p>It’s essential to establish customer desirability early (and cheaply). Most innovation labs will be well accustomed to experimenting, but such experiment efforts need to be supersized. By industrialising the experimentation process it’s far more likely you will uncover successful value propositions.</p><p>Industrialised experimentation should be an ‘always on’ process. Week in, week out continually experimenting in order to validate hypotheses.</p><p>As part of your territory identification, user research (user journeys, ethnography, proto-personas etc) and competitor landscape, you should be able to create hundreds of hypotheses. The key to this is the specificity of the hypothesis.</p><p>The more specific the hypothesis, the easier it will be to build an experiment to validate whether it is true or not.</p><p>Due to the volume of experiments being run (1–2 per week per team), you must ensure you’re validating hypotheses in the lightest possible way. Sign-ups from simple smoke tests or ghost features should provide data to establish any signals of intent from real customers. Building out technology should not be a concern at this stage — why waste time/money on building something if nobody wants it?</p><figure><img alt="Fake cut-out of a saloon" src="https://cdn-images-1.medium.com/max/600/0*ogYO4STMXpcABxzS.png" /></figure><p>Use smoke tests to identify signals of intent</p><p>At this point, you have to be brutal, no matter how much you like an idea. If there is no evidence to support your hypothesis, kill it immediately and move onto the next experiment. Don’t be distracted by confirmation bias — i.e. the ability to embrace evidence that confirms our beliefs, while ignoring/rejecting evidence that casts doubt on it.</p><p>Only when you have indisputable data supporting your hypothesis should you look to progress an idea. Only use technology when absolutely necessary to build out the proposition. Manually run processes that at a later point you may automate (aka concierge MVP’s). Throughout building out ideas, maintain a learning mindset and be ruthless about killing the ideas when data doesn’t support the hypothesis</p><p><strong>Metrics</strong></p><p>Many teams struggle when it comes to measuring innovation. Some will default to measuring revenue, but this is the wrong metric to focus on. Revenue is a lagging indicator and tells you what has happened in the past. It is also affected by external factors that may have nothing to do with your innovation efforts.</p><p>Product success relies on measuring meaningful metrics — a North Star so to speak. To determine your North Star metric you must look at how your product delivers value to your customers. North Star metrics are usually linked to your customer&#39;s engagement with your product, and the direction it provides will likely be the single largest driver of growth. Your North Star metric is never revenue.</p><p>Once you have arrived at your North Star metric break it into actionable input metrics:</p><ul><li>Breadth — How many active/returning users are taking this action?</li><li>Depth — What’s the depth of their engagement?</li><li>Frequency — How often does each user engage?</li><li>Efficiency — How fast do they succeed?</li></ul><p>Mapping these will help you understand your customer interactions and what they truly value. It also helps align your priorities and provide focus for your teams. All efforts should go into moving the needle for this single metric.</p><p>By making this metric clear and transparent will ensure those around you also know exactly what success looks like.</p><p><strong>Metered funding</strong></p><p>Innovation requires a different funding model for traditional budgetary practices. Metered funding is a tried and tested practice commonplace in the world of startups. Essentially, funds are allocated over a series of rounds, initially based on learnings and latterly on growth.</p><p>Metered funding works hand in hand with industrialised experimentation. Small amounts of funds are readily available to experiment encouraging teams to innovate. This process mitigates the risk of running up hundreds of thousands of pounds of investment into projects that will, in all probability, amount to nothing.</p><p>Further (and potentially larger) funding is allocated only when learnings have been made (i.e. initial hypotheses have been validated). This ensures only propositions that show real potential can progress.</p><p><strong>Learn by doing</strong></p><p>Expensive training courses that promise to ‘teach innovation’ are just that: Expensive training courses. In my experience, spending hours or even days in workshops won’t radically change your day to day activities.</p><p>“I hope you’ve enjoyed the workshop, now get back to your day job”.</p><p>Such courses usually don’t stick. With an understanding of the basics, it’s far better to just get your hands dirty and give it a go. You will learn far more from your own mistakes than you ever will in a classroom.</p><p>It will be challenging and there will be bumps in the road, but the best way to learn is by doing. Just do it!</p><p><strong>In summary</strong></p><p>Creating a culture of innovation is hard and you will struggle to do this alone. Building a successful, repeatable, innovation process requires senior leadership buy-in (ideally they will drive it).</p><p>Avoid innovating in silo’s by creating small and nimble teams that are embedded throughout the organisation. These teams sole role is to focus on experimenting to validate new opportunities/ideas.</p><p>Understand the goals of your organisation. Aligning innovation efforts to these goals will be a crucial factor in the success of any new product or services — winning support for innovations that potentially cannibalise existing products/service will be very difficult unless your organisation is truly looking to disrupt themselves.</p><p>Industrialise experimentation. Make hypotheses really specific and continuously run lightweight experiments to validate your assumptions.</p><p>Measure only the metrics that matter. Be transparent and define what metrics add real value to customers. Chase these instead of revenue.</p><p>Work with your finance teams and set up a metered funding model that encourages innovation with small, readily available, funds to experiment. As desirable products emerge, release further funds to validate the feasibility and viability of ideas.</p><p>You don’t need an innovation lab. You (and your organisation) may just need a shift in mindset.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4ca90669a03" width="1" height="1" alt=""><hr><p><a href="https://medium.com/red-badger-thinks/innovation-without-the-lab-4ca90669a03">Innovation (without the) Lab</a> was originally published in <a href="https://medium.com/red-badger-thinks">Red Badger thinks</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Red Badger launches ShareThyme — an innovative new platform]]></title>
            <link>https://medium.com/red-badger-thinks/red-badger-launches-sharethyme-an-innovative-new-platform-14c06b6cb168?source=rss-2cc5610543dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/14c06b6cb168</guid>
            <category><![CDATA[delivery]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[scaling]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[product]]></category>
            <dc:creator><![CDATA[Red Badger]]></dc:creator>
            <pubDate>Thu, 01 Aug 2019 10:24:25 GMT</pubDate>
            <atom:updated>2019-08-01T10:24:25.729Z</atom:updated>
            <content:encoded><![CDATA[<h3>Red Badger launches ShareThyme — an innovative new platform</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ES9jS6OgusfSVeD75mXlEw.jpeg" /><figcaption>Tommy &amp; Monju, two users of ShareThyme</figcaption></figure><p><strong>Why we’re gathering the generations together</strong></p><p>More than <a href="https://www.ageuk.org.uk/information-advice/health-wellbeing/loneliness/">3.6 million</a> elderly people in the UK live alone, and more than a <a href="https://www.nhs.uk/conditions/stress-anxiety-depression/loneliness-in-older-people/">million</a> say they go for over a month without speaking to a friend, neighbour or family member. According to research, this has a real impact on their health and life expectancy.</p><p>Through ShareThyme, we’re on a mission to help make things better by bringing people together through food.</p><p><strong>Cooking up connections</strong></p><p>Becoming part of the ShareThyme community is simple. Older adults (teachers) create their teacher profile on the platform. This includes a short bio to introduce themselves to students, as well as their favourite recipes and a list of ingredients.</p><p>Once their profile’s live, younger people (students) can visit the teacher’s profile and request a cooking class from the teacher to learn one of their dishes.</p><p>If the teacher’s happy to meet the student, ShareThyme will connect them. Both the teacher and student will receive a confirmation of the session and we’ll assist them in finding a time, date and a suitable place to meet, cook and connect.</p><p><strong>The story that sparked ShareThyme</strong></p><p>Social value projects have always been close to our hearts and we’re all very keen to use our skills for creating social impact where we can. Previous social initiatives included Anthony Nolan, Music for My Mind or building last year’s Pride in London app.</p><p>We spend our days helping companies build wildly successful products in some of the toughest business environments. We’ve learned what works and what doesn’t and how to get innovative new ideas built and launched to market.</p><p>We have a Product Strategy process that makes it possible to conceive, test, develop and launch new ideas in 2 weeks flat and we wanted to prove it can be used to achieve anything.</p><p>We’ve developed ShareThyme as a non-profit project, inspired by a friend’s beautiful story. Monju (79) randomly bumped into Tom (32) in a supermarket and offered to teach him how to cook various Bangladeshi curries in her home. After hearing their remarkable story, Red Badger did some research and discovered there was a gap waiting to be filled by an online platform that connects people through the love of cooking. ShareThyme was born.</p><p><strong>Red Badger’s special sauce</strong></p><p>It took us just 8 days to build ShareThyme, by bringing together a fully cross-functional Badger team and our Product Strategy process. The project’s success shows how an innovative platform can be built at speed and scale, without risk.</p><p>It’s still early days and we’re experimenting with the concept to learn from our MVP (minimum viable product) through testing with users. We’re delighted to have developed this platform in such a short amount of time.</p><p>And, most importantly, seeing the amazing positive impact it’s having is truly inspiring. Already, inspiring stories are mounting up, as teachers and students connect and bond. We’re gathering some of these stories together. Read them at <a href="https://sharethyme.co.uk/stories">sharethyme.co.uk/stories</a></p><p><strong>So what’s next on the menu?</strong></p><p>We’re committed to ensuring the success of the platform and seeing the project help more people connect through cooking. In year one we’re on track to bring over 1,000 people together across 30 countries. Through the platform, we’ll provide older people with 1,500 hours of time spent cooking with a new friend — time that might have been spent alone.</p><p>We believe this is the beginning of something big. We’re now starting to promote the platform nationwide and are seeking partnerships to help us continue to grow ShareThyme.</p><p><strong>Get a taster</strong></p><p>Want to get involved? Become part of the ShareThyme community now at <a href="http://sharethyme.co.uk/">sharethyme.com</a> or get a flavour of how we built the platform <a href="http://red-badger.com/sharethyme">here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=14c06b6cb168" width="1" height="1" alt=""><hr><p><a href="https://medium.com/red-badger-thinks/red-badger-launches-sharethyme-an-innovative-new-platform-14c06b6cb168">Red Badger launches ShareThyme — an innovative new platform</a> was originally published in <a href="https://medium.com/red-badger-thinks">Red Badger thinks</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Red Badger journal — My first week]]></title>
            <link>https://medium.com/red-badger-thinks/red-badger-journal-my-first-week-1b34e5d44142?source=rss-2cc5610543dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/1b34e5d44142</guid>
            <category><![CDATA[first-day]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[redbadger]]></category>
            <category><![CDATA[new-job]]></category>
            <dc:creator><![CDATA[Red Badger]]></dc:creator>
            <pubDate>Tue, 04 Jun 2019 16:47:51 GMT</pubDate>
            <atom:updated>2019-06-13T14:01:05.007Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Red Badger journal — My first week</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*G9ZtsMpkxOjKLkmW.jpg" /></figure><p><strong>Dear diary, my first 5 days…</strong></p><p>In May 2019 I decided to make the next step in my career and landed a job with Red Badger. Starting any new job fills you with all kinds of emotions, from excitement to nervousness. A new venture full of unknowns can make it seem scary, like it’s the first day of school all over again!</p><p>I wanted to jot down some notes of how my first week with Red Badger went to provide some insights for other newbies in future. I’ll run you through day by day, in true teenage blogger style summarising each of my first 5 days. At the same time I’ve pulled out some useful bits of information and tried to answer any questions I had in my head before joining.</p><p><strong>Day 1: Reliving the first day of school all over again</strong></p><p>Coming out of Old Street station, the first thing I did was to find the office. Thankfully it’s less than a minute walk from the tube, meaning it’s pretty easy to find. On arriving, one of the people advisors ran me through some of the basics and got me set up with my mac which I had pre-ordered a few weeks before joining. After setting up my emails, I was given a trello onboarding task list and shown the HQ information site.</p><p>Later I met my buddy who was on hand to answer all the silly first day type questions. They also gave me a tour around the office and introduced me to the project team which I was going to be part of including some of the exciting work we would be doing. In addition to a buddy to get you settled in, I was also told about mentoring which is available to everyone, where you can check in regularly with someone who can give advice for your career. I met a few fellow new joiners while having lunch in the kitchen area, which made me feel like I’m not the only one trying to take in all this new information. At the end of day 1 exhausted and tired, I had one last introduction to make which was the adorable office dog MILO!</p><p><strong>Day 2: The power of chocolate</strong></p><p>I wanted to say thank you for the warm welcome I had received from my team and say hello to a few others around the office, so I decided to use the power of chocolate including mini flapjacks and crispy cakes as a great icebreaker which introduced me to the different teams based at HQ. This helped me understand where the people, recruitment and operations, finance and events were and opened up some great conversations.</p><p>After lunch, I dived into the detail of HQ information. An internal site which has a range of info including some background on the company, culture and brand. A section focused on your career development and how to progress. Then the standard but important things like where to find your timesheets, expenses and payslips. Finally your benefits and which kick in after probation period, if your unsure about any these be sure to ask before joining. To have everything about a company located in one place was refreshing and gave good detail on all those silly new starter questions you have in your head when starting at a new place.</p><p><strong>Day 3: Happy Birthday Red Badger</strong></p><p>Started the day having a 1–2–1 with my line manager. I was given a run through on all things I need to know from monthly company meetings, peer reviews to how the annual training budget could be spent. We also took time to get to know each other and later in the day sent out my welcome email to everyone. It’s a great way of introducing yourself to the company.</p><p>Lunch involved discovering the local Whitecross street food market. In the afternoon, it was time for celebrations as it was Red Badgers 9th birthday. Cake and balloons waere a great way to finish off a Friday and get everyone ready for the weekend. Today I also received my phone for work and personal use. I got the option between the latest iPhone, Samsung or Google Pixel. After researching which would be the most beneficial, I took advantage to make the jump from IOS to Android and got a Samsung S10.</p><p><strong>Day 4: Tiki tour (without the Piña colada)</strong></p><p>With my first 5 days being split by a long bank holiday weekend, I had the chance to let things sink in and start my next week. I had been booked in on a ‘tiki tour’ in the morning. I must admit, being told we weren’t going for an early Piña colada cocktail with a fresh slice of pineapple to start the day was a shame. Turns out a Tiki Tour is where you head off to a project and someone from the team will take an hour out of their day to run you through the work being completed, show you round the client site and spend some time to catch up. Really valuable, open to anyone and a great way to learn more about some of the interesting work going on.</p><p><strong>Day 5: Onwards and upwards</strong></p><p>Really getting into full swing now, kicked off the day with a weekly team catch up. After a restructure of the business recently into separate P&amp;Ls things are still in experimental mode with teams being called a few variations. The names haven’t been finalised and it feels good to be at a place that as it grows they are open to how teams work and are allowing employees to help share and get things in the right place to maintain the culture that exists. Later I had a catch up with my MD and we ran through how teams are structured in more detail, what projects I would be involved within my first few months and options for my own career development.</p><p><strong>Summary</strong></p><p>So how did I find my first week? Overall it has been AWESOME! A really enjoyable experience which has felt like a whirlwind. A mix of highs and lows, feeling tired from the sheer amount of new information you have to take in as is the case when starting any new job and a little stressful as the understanding slowly starts to fall into place. What has helped massively is there is a supportive environment. I’ve found I haven’t asked a question which has been seen as silly or anyone not willing to help me in finding out the answer. I know it’s only 5 days but feels like I have made the right move for the next stage of my career. Looks like I will have many opportunities to be part of creating great digital products and services while also being able to develop myself and learn some new things along the way!</p><p><em>Originally published at </em><a href="https://blog.red-badger.com/red-badger-journal-my-1st-week"><em>https://blog.red-badger.com</em></a><em> on June 4, 2019.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1b34e5d44142" width="1" height="1" alt=""><hr><p><a href="https://medium.com/red-badger-thinks/red-badger-journal-my-first-week-1b34e5d44142">Red Badger journal — My first week</a> was originally published in <a href="https://medium.com/red-badger-thinks">Red Badger thinks</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[We are just 1 year shy of a decade of Badgeriness]]></title>
            <link>https://medium.com/red-badger-thinks/we-are-just-1-year-shy-of-a-decade-of-badgeriness-45765d0ff796?source=rss-2cc5610543dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/45765d0ff796</guid>
            <category><![CDATA[company-culture]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[company-values]]></category>
            <category><![CDATA[empowerment]]></category>
            <category><![CDATA[growth]]></category>
            <dc:creator><![CDATA[Red Badger]]></dc:creator>
            <pubDate>Fri, 10 May 2019 10:31:33 GMT</pubDate>
            <atom:updated>2019-05-10T10:31:33.239Z</atom:updated>
            <content:encoded><![CDATA[<h4>Culture is at the core of what will make your company a great one</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uLyYxVEpIQBQbhsedc462g.jpeg" /></figure><p>It’s that time of year again. May 4th when Red Badger has another birthday. We are now 9 years old. Last year’s 8th Birthday <a href="https://blog.red-badger.com/2018/5/24/red-badger-eight-years-and-maturing-nicely">Blog</a> was a little retrospective of some of the changes we’d been through in the past 12 months and alluding to the future. We’ve been implementing a new strategy, including the largest re-structure to the business in our 9-year history which resulted in the creation of lots of new roles and 15 internal promotions. We are also developing new value propositions to evolve the business and the service we can provide in helping our clients. A lot of the change is still panning out. It’ll take 2 years for some of the changes to have embedded themselves before we can really know how they’ve gone so I think next year might be more appropriate to update you on that. For this year’s birthday blog, I have taken a few snippets from a talk I gave recently about Culture and Leadership. I could write a book’s worth of content on what we have done at Red Badger around Culture and Leadership but for the purposes of this blog post, I have kept it reasonably brief.</p><h3>#1 — VALUES: Bind people to a common cause — bottom-up culture is key.</h3><p>A key factor in accelerating alignment is involving your employees in the development of your culture. If they are involved, they feel a part of the eventual outcomes. At Red Badger, we work hard to empower our employees to develop our culture, bottom-up. With lots of differing opinions, this can take a long time but it is worth it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M78INfGLVFz405v3TtezgA.png" /><figcaption>The criteria we set for setting out our vision</figcaption></figure><h3>#2 — ACTIONS: Actions speak louder than words</h3><p>Many companies have a vanilla set of values that they print on the wall and tell their employees that this is what it means to work at your company. Their behaviour exhibits something entirely different. It is extremely important that the work you do with your employees to build a bottom-up culture doesn’t go up on the website and become externally facing only. You have to live and breathe culture. It has to become embedded in everything you do and your actions have to speak louder than words.</p><h3>#3 TRANSPARENCY: Make information open and transparent</h3><p>We try to keep all of the company up-to-date and involved with the future of the company. We have a number of forums (e.g. a yearly company day and a company meeting at HQ every 3rd Friday of the month) where our employees get the chance to shape the future of the company and are then kept up-to-date with progress against the plan.</p><p>At these forums we can share whatever is interesting, sometimes this is employee driven, sometimes it is leadership driven. Nothing is off limits.</p><p>We share the Red Badger Strategy and our progress against the plan. We share our financial information, our revenues our profits and our investment decisions as well as other core business metrics such as sales performance and recruitment performance. We also include people related initiatives such as gender balance and gender pay gap as well as other Equality, Diversity and Inclusion metrics. We are very open and transparent about where we are doing well and where we have clear room for improvement.</p><p>By doing this, we can teach people the meaning of measures and reports. We can teach them how a business is run and how they can provide impact. Feeling like they are part of a bigger whole, is the definition of Purpose.</p><h3>#4 TEAMS — Organise around a network of accountable teams, not centralised functions</h3><p>Prior to the restructure that I mentioned in the intro, we had more of a traditional centralised function, with one leadership team. This became unwieldy as we grew and we were unable to support all of our employees appropriately.</p><p>Our answer was a process of devolution, effectively breaking the company up into separate P&amp;Ls (We haven’t yet finalised the naming of these P&amp;Ls. For the purposes of this blog, I will call them Setts as in the Badger’s den) each with their own leadership team. Our primary reason for doing this was to make sure that all of our employees were well looked after.</p><p>In the new structure, we created a leadership team in each Sett to line manage the cross-functional teams that sit within each Sett. We promoted 15 people from within to fill the roles. The data in the feedback now tells us that our employees feel like they are looked after more, they feel like they belong to a Sett as well as the company as a whole. They are empowered to set their own Sett goals and objectives such as which sectors they would like to work in. The rest of the organisation has now flipped to support the Setts rather than the other way round.</p><p>The core services (Finance, Legal, People &amp; Culture, Sales &amp; Marketing etc…) have now switched to being Sett driven. The Setts communicate what they need to the core services and the core services execute the requirements. Previously, sales and recruitment were pushed downwards to the delivery teams.</p><p>Now accountability flows from Leadership to the Setts. Leadership set a high-level strategy. The Setts are responsible for formulating and executing the strategy. The core services provide the enablement. We’ve effectively created a new social structure of self-governing entities that are fully accountable.</p><p>The energy and drive that it has brought to Red Badger has been incredible to see. There are a few more tired faces around the office because the leadership of the Setts have far more responsibility and are having to learn a lot of new things. But they are rising up to the challenge with new vigour.</p><h3>#5 TRUST — Trust teams to regulate and improve their performance</h3><p>Now the structure is in place, we have to provide the teams with real autonomy over decision making and problem-solving. We eliminate bureaucracy and empower them to continuously improve.</p><h3>#6 LEADERSHIP: Your horizons have to grow (or the companies won’t)</h3><p>I really like this quote from Herb Kelleher, former CEO and founder of Southwest Airlines. “Leadership is being a faithful, devoted, hard-working servant of the people you lead and participating with them in the agonies as well as the ecstasies of life”.</p><p>Leadership is all about empowering others, leading by example, working with people and being there to help when necessary. A leader doesn’t just see people as assets. They really care about people and their best interests. A leader elevates employee’s lives both at work and outside of work. They are trustworthy, give great feedback, support and help others to reach their full potential.</p><p>Leaders need to provide high-level strategic direction but then delegate and provide autonomy and accountability to their employees to formulate and execute the strategy.</p><p>However, they will not be able to do this alone. Great leaders can build other great leaders. They will need to hire and build other leaders in their company to be the gatekeepers of the culture. They, in turn, will then build other great leaders who will embody and maintain the culture. Leadership is the foundation of this cycle.</p><p>If you align everyone around your culture and provide the appropriate leadership to support it, you will be able to maintain a great culture as you grow.</p><h3>CULTURE IS THE CORE OF WHAT WILL MAKE YOUR COMPANY A GREAT ONE</h3><p>At the core of every great company is a great culture. The cultures from company to company vary widely. There is no single answer for what your culture should be. But as you grow, your culture will change and you will need to evolve with it.</p><p>It’s hard. Red Badger is continuously improving but our culture often feels at breaking point. But constantly feeling like your culture is at breaking point is a good thing. Because as long as you feel like it is about to break, the more vigilant you will be in looking after it. And it does need constant looking after.</p><p>If you get it right and you build a great culture, you will be able to unleash huge amounts of ambition, courage, creativity and collaboration in your company.</p><p>To build a really strong culture empower your employees to develop your culture bottom-up and then build all of the pieces of your company around it. You also need to align everyone around a noble vision. Listen to your employees, communicate with them clearly and embed your culture in everything you do. Actions speak louder than words. Your employees need to feel like there is progress against the things you say you’re going to do.</p><p>Finally, build appropriate levels of leadership to be the guardians of your culture and to make sure that everyone lives and breathes it. With all of the pieces in place, you will be able to empower others, trust them and delegate. Then you will have the foundations in place, to grow a fantastic company, department or team.</p><p>If you’d like to discuss Culture &amp; Leadership with me, feel free to contact me on <a href="/service/mailto: cain.ullah@red-badger.com">cain.ullah@red-badger.com</a>.</p><p>Also, if you’re fancy becoming a Badger, check out the open roles <a href="https://red-badger.com/jobs">here</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=45765d0ff796" width="1" height="1" alt=""><hr><p><a href="https://medium.com/red-badger-thinks/we-are-just-1-year-shy-of-a-decade-of-badgeriness-45765d0ff796">We are just 1 year shy of a decade of Badgeriness</a> was originally published in <a href="https://medium.com/red-badger-thinks">Red Badger thinks</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Programming a quantum computer: generating true random numbers]]></title>
            <link>https://medium.com/red-badger-thinks/programming-a-quantum-computer-generating-true-random-numbers-8f3f04f09f0c?source=rss-2cc5610543dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/8f3f04f09f0c</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[redbadger]]></category>
            <category><![CDATA[science]]></category>
            <category><![CDATA[quantum-computing]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Red Badger]]></dc:creator>
            <pubDate>Mon, 15 Oct 2018 14:41:40 GMT</pubDate>
            <atom:updated>2019-06-13T13:41:28.005Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rTiEefXBL6_UYuR9.jpg" /></figure><p>Computers are deterministic, predictable machines and are designed to blindly follow sets of instructions in a repeatable manner. This nature of computers has of course served us extremely well through most of the last century, but this design comes with a fundamental flaw: it cann ot perform random operations [ <a href="https://blog.red-badger.com/blog/2018/9/24/generate-true-random-numbers-with-a-quantum-computer#ref:4">1</a>]. Random number generators are an extremely important component of many applications today, but whilst the numbers they generate might be random enough, they are “pseudo” random and are often possible to predict or reverse engineer in some way.</p><p>Today it is possible to harness the strange, unpredictable nature of subatomic particles and use them to perform calculations inside a quantum computer. With just a few lines of code we can program a real quantum computer to generate true random numbers for us. Something previously impossible using a classical, Turing based computer.</p><h3>Random number generators today</h3><p>Most popular programming languages have some form of random number generator built in for developers to use. These generators generally take an input seed representing the current date and time, scramble this value up using an algorithm, and output a value so different from the input that we perceive them as random. The scrambling function is a predictable algorithm with a high amount of entropy (for a small change in input they return a large change in output), and we get a different number out each time because the input seed changes over time. For almost all practical applications this system works perfectly well, but since it’s a predictable system it isn’t truly random.</p><p>Let’s take the random number generator provided by Javascript as an example. First of all, since Javascript is a language interpreted in different environments (browser or node.js), it’s up to the interpreter to decide on what algorithms to use that conform to the ECMAScript spec. Today, most modern browsers use the same randomness algorithm to power Javascript’s Math.random() function called xorshift128+.</p><p>Here is a general version of this algorithm written in C [ <a href="https://blog.red-badger.com/2018/9/24/generate-true-random-numbers-with-a-quantum-computer#ref:1">2</a>]:</p><p>The purpose of this code is to take some input (the seed) and scramble it to such a degree that any two outputs from the two separate inputs will seem completely different to each other and therefore random. The algorithm achieves this by shifting the seed’s binary representations up and down and reversing the bit representations in between steps, resulting in a bit representation of a number completely different from the seed input.</p><p>In order for this function to provide different results each time it is run, we need an always changing seed. Browsers (and other programming languages) often simply use a numerical representation of the current date and time [ <a href="https://blog.red-badger.com/2018/9/24/generate-true-random-numbers-with-a-quantum-computer#ref:5">3</a>], for example the UNIX epoch time, the number of milliseconds that have elapsed since 1 January 1970 [ <a href="https://blog.red-badger.com/2018/9/24/generate-true-random-numbers-with-a-quantum-computer#ref:6">4</a>].</p><p>With this seed, and the high entropy algorithm above, we can achieve a very convincing random number generator. Computer systems use these functions all the time without issue, but we cannot call it a truly random number generator. If somebody knows how the random number generator works, and can predict the input seed, they can also predict the output of the function. One way to improve the randomness of this system is by making the seed harder to predict. For example, many systems use the cosmic microwave background radiation (the electromagnetic radio waves still left over by the big bang) as a seed [ <a href="https://blog.red-badger.com/2018/9/24/generate-true-random-numbers-with-a-quantum-computer#ref:7">5</a>] since nobody can predict how this background noise will behave at any given point in time.</p><p>A randomness system using an unpredictable seed like the microwave background is at this point totally random by today’s knowledge. Nobody currently can predict how this seed will behave at any given point in time, and so cannot predict the random number it generates. This type of seed may even be impossible for us to predict in the future, but if we have the same measurement of the cosmic microwave background as somebody else and use it as an input to the random number generator we will be able to predict their result.</p><p>To generate a truly random number we need to find something in nature that we cannot perfectly predict, something that can only be described by probability. Until the early 20th century this was believed not to exist, but the theory of quantum mechanics opened doors to an even stranger and unpredictable world.</p><h3>Probability in the quantum world</h3><p>Quantum mechanics is a theory which describes the nature of particles on the subatomic scale. It says that as we observe the world at a smaller and smaller scale, classical descriptions of particles and forces like those defined by Sir Isaac Newton in the 18th century become less accurate and we must switch to different quantum descriptions driven by statistics and probability. For example the exact position of an electron around an atom cannot be predicted, we can only predict the probability of finding an electron in a given area around the atom at a given time [ <a href="https://blog.red-badger.com/2018/9/24/generate-true-random-numbers-with-a-quantum-computer#ref:8">6</a>].</p><p>To make things even stranger, the Copenhagen Interpretation of quantum mechanics devised by Niels Bohr and Werner Heisenberg states that quantum systems do not have definite properties prior to being measured, but exist in all possible states simultaneously in a principle known as superposition. It is only when the system is observed that the superposition collapses and the system exists in a single definite state. This is known as the observer effect. Taking the example of the position of an electron, we can predict a probability that an electron will be present in a particular location at a particular time, but before that measurement the electron exists in all possible positions around the atom. During the measurement the electron will reveal itself to be in one place, but by observing and measuring the electron we have altered its state and cannot determine other properties like momentum due to the uncertainty principle [ <a href="https://blog.red-badger.com/2018/9/24/generate-true-random-numbers-with-a-quantum-computer#ref:9">7</a>].</p><p>This interpretation of the quantum world understandably shook the physics community at the time, and is debated to this day. Einstein refused to believe that reality is governed by probability and famously said “I, at any rate, am convinced that He (God) does not throw dice” and “Do you really think the moon isn’t there if you aren’t looking at it?”. In response, Niles Bohr later responded “Einstein, don’t tell God what to do.” [ <a href="https://blog.red-badger.com/2018/9/24/generate-true-random-numbers-with-a-quantum-computer#ref:10">8</a>]</p><p>Like it or not, Quantum theory remains our best understanding of the subatomic world and has been developed into the heart of an all new type information processor. Quantum computers rely on the ability for quantum particles to exist in a superposition of multiple states at once to perform calculations. Since quantum computers can manipulate the superpositions of particles which are governed by probability, we can use them as a tool to harness the nature of the quantum world and build a true random number generator.</p><h3>Qubits and quantum gates</h3><p>Classical computers use binary digits, or bits, to represent information. A bit can take the values 0 or 1 and are represented by one of two levels of DC voltage inside a computer processor. Quantum computers usually represent information the same way, using a 0 or 1 bit, but they physically implement these states using binary properties of subatomic particles. These properties might be the spin of an electron (spin up and spin down) or the polarisation of a photon (horizontal and vertical polarisation). Either of these representations can be described by quantum mechanics, and can be in a superposition of both states at once [ <a href="https://blog.red-badger.com/2018/9/24/generate-true-random-numbers-with-a-quantum-computer#ref:11">9</a>]. This means that a quantum bit of information, or qubit, can exist in a superposition of both states 0 and 1 at the same time. To measure the result of a computation, we must measure the quantum state inside the computer and force these particles to choose a 0 or 1 state.</p><p>To manipulate qubits in a quantum computer we use quantum gates much like the gates of a classical circuit. Whilst a classical computer can perform operations on bits such as flipping them to their opposite value, quantum gates can do these operations and more advanced quantum operations such as pushing a qubit into a superposition of both possible values. A gate that pushes a qubit into a superposition is called a Hadamard gate and is one of the most fundamental and commonly used logic gates in quantum computing [ <a href="https://blog.red-badger.com/2018/9/24/generate-true-random-numbers-with-a-quantum-computer#ref:12">10</a>].</p><p>When we push the spin of an electron into a superposition of both possible spin up and down states representing the values 1 and 0 of a qubit, the electron can be said to have a simultaneous spin of both values, and the qubit is in a superposition of 0 and 1. When measuring this qubit, we collapse the superposition and force it into one of these two possible states, each with an equal probability of occurring [ <a href="https://blog.red-badger.com/2018/9/24/generate-true-random-numbers-with-a-quantum-computer#ref:13">11</a>]. With each superposition and measurement we have a 50% chance of measuring either 1 or 0. We would then have performed the equivalent of a coin flip using the fundamental laws of the subatomic world.</p><p>In order to generate our random number from a quantum coin toss all we need to do is:</p><ol><li>Get a qubit with a predefined state. Either 0 or 1 will do.</li><li>Force that qubit into a superposition using a Hadamard gate.</li><li>Measure the state of the cubit.</li><li>Obtain a value of 0 or 1 with equal probability.</li></ol><p>Now all we need to do to create our true random number generator is get access to a quantum computer and program in the above steps.</p><h3>Programming a quantum computer</h3><p>Amazingly, some companies have now made simple quantum computers available in the cloud for use by the general public. One of these services is provided by IBM and is called <a href="https://quantumexperience.ng.bluemix.net/">IBM Q Experience.</a> Currently this service provides access to two 5 qubit processors and two 16 qubit processors distributed around the globe. Once user’s have created a free account, computation time is allocated using a credit system, and free users are given a small number of credits to use that refresh each day. You can design your circuit using an online editor or programatically via an SDK (16 qubit processors are currently only available to users of the SDK), and when your program is ready to execute it is put into a queue to be run when the processor is next available.</p><p>To build our random number generator we will use the provided SDK for IBM Q Experience called <a href="https://qiskit.org/">Qiskit</a>. We will need to write our code in Python, and whilst writing the application we will also be able to test it on a simulated quantum processor locally on our own machine to save time and credits.</p><p>First let’s start with the basic code to complete the four steps above:</p><p>Here we create a quantum circuit from two single bit registers, one quantum register with a single qubit and a similar sized classical register for interacting with the quantum register. We then apply a Hadamard gate to our single qubit to force it into a superposition state, and measure that state on to our classical register. Finally we execute the process we just described on a local simulated processor, telling the SDK to only run the process once. For most other purposes, we would want to run a quantum circuit multiple times and average out the results to eliminate the inherent randomness in the system, but for our purposes just a single run will work perfectly. We can print out the counts of our results, which will display as a map of possible bit values to the number of times they were measured for each run e.g: { “0”: 1, “1”, 0 }. You will find that once this program is run on a quantum processor, the measurement of a 0 or 1 value will occur with 50% probability.</p><p>This code has given us the equivalent of a perfect coin toss, so now all we need to do is find a way to take a series of binary coin tosses and convert them to a random number in a given range. An easy way to do this is to take the random bit values we generate with the code above and put them together in sequence to create a binary number. When we convert this binary number to decimal we will find that it will be a random decimal every time.</p><p>If we are going to allow input from a user to choose a range for generating our number, we will need to figure out how many bits are required to represent a given base 10 integer so we know how many random bits to generate. The equation we need to do this is [ <a href="https://blog.red-badger.com/2018/9/24/generate-true-random-numbers-with-a-quantum-computer#ref:2">12</a>]:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/188/0*0GsPC765Hbg9KM3T.png" /></figure><p>Which we can represent in python as the function:</p><p>Using this we can write a function that generates a random number to a given maximum by repeating the quantum circuit above for each bit that we require:</p><p>This code is the core of our quantum random number generator. We calculate the number of bits required to generate a number up to the given maximum, and for each required bit we generate a random value using Qiskit and add it on to a string of generated bits. We then parse this string as a base 10 integer from base 2.</p><p>However there is a crucial problem with this code; if you run it enough times you will realise it actually generates numbers up to a maximum of the next nearest power of two to the input. This is because we have calculated how many bits are required to represent a given number, but if all these bits have the value 1, then our number could easily be higher than the given maximum. It’s surprisingly difficult to solve this problem, and the best way to keep the number below our maximum without introducing some other statistical bias is using rejection sampling [ <a href="https://blog.red-badger.com/2018/9/24/generate-true-random-numbers-with-a-quantum-computer#ref:3">13</a>]. We would simply need to generate a number, and if it was too large reject that number and run the process again. Since we have limited resources on a free account with IBM Q Experience, we will keep our code simple and just restrict the users’ input to powers of two by rounding up the input to the next highest power:</p><p>We can also quite easily parse command line input from a user to take in a desired maximum, as well as a flag to tell the program whether to run on a real quantum computer and an option to pass an API key for IBM Q Experience:</p><p>Finally, before we can run our code on a real quantum processor, it would be best to optimise our solution to loop a minimal number of times to save on free resources on our cloud quantum processor. As an example, if we were to use the 5 qubit processor “ibmqx4” situated in Tenerife, we could utilise all 5 qubits by passing all of them through Hadamard gates and combining their values when measured. This would allow us to generate a random number up to 31 with a single loop, and IBM Q Experience provides enough credits for 3 instructions allowing us to generate a number up to 32767 in a single run.</p><p>With all of these elements combined, our final code becomes:</p><p>The full code and a description on how to run it can be found on <a href="https://github.com/robbiemccorkell/quantum-random-number">GitHub</a>.</p><h3>What just happened?</h3><p>If you sign up for a free account with IBM Q Experience, get an API key and run this program like so:</p><pre>&lt;code&gt;python ./main.py -remote --qx-token &amp;lt;your-token&amp;gt; 15&lt;/code&gt;</pre><p>you will find the process will take some time to run (approximately 10–20 minutes) and return a random integer between 0 and 16. Here is what happened while you were waiting:</p><ol><li>Your computer parsed the command line input and calculated how many random bits are required to represent a number between 0 and the next power of 2 from 15. In this case 4 bits are required to build a number up to 16, which means only one instruction to send to a 5 qubit quantum processor.</li><li>A series of instructions are built by the Qiskit SDK and sent to IBM Q Experience to be executed.</li><li>Your instructions are placed in a queue to be run by the “IBM Q5” quantum computer in Tenerife.</li><li>Once ready, the IBM Q5 Tenerife quantum computer allocates 4 of 5 available qubits to the requested task. It applies a Hadamard gate to these 4 qubits, entering them into a superposition of quantum spin.</li><li>The spin of each qubit is them measured, colllapsing the quantum superposition and revealing a random binary state which is then output to a 4 bit classical register.</li><li>The measured binary state is then sent back to IBM Q Experience, and back to the Qiskit SDK running on your computer.</li><li>Your computer takes these binary measurements and builds a 4 bit binary number out of them.</li><li>Your binary number is converted into a base 10 integer and returned to the user.</li></ol><p>Congratulations, you have just controlled a quantum computer and harnessed the strange unpredictable properties of subatomic particles to generate a true random number. Please consider using your newly found superpowers for good.</p><p>Know of some interesting practical applications for cloud quantum computing? Let me know <a href="https://twitter.com/robbiemccorkell">@robbiemccorkell</a>.</p><p>We’re always on the lookout for prospective Badgers, so if you like the look of us, we’d love to hear from you. All our current vacancies can be found <a href="https://red-badger.com/jobs">here</a></p><p>References:</p><ol><li><a href="https://engineering.mit.edu/engage/ask-an-engineer/can-a-computer-generate-a-truly-random-number/">Jason M. Rubin, MIT School of Engineering (2011), Can a computer generate a truly random number?</a></li><li><a href="https://hackernoon.com/how-does-javascripts-math-random-generate-random-numbers-ef0de6a20131">Daniel Simmons, Hackernoon (2014), How does JavaScript’s Math.random() generate random numbers?</a></li><li><a href="https://bocoup.com/blog/random-numbers">Adam Hyland, bocoup (2013), Random number generation in Javascript</a></li><li><a href="http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap04.html#tag_04_16">The Open Group Base Specifications Issue 7 (2018), 4.16: Seconds Since the Epoch</a></li><li><a href="https://arxiv.org/abs/1511.02511">Jeffrey S. Lee, Gerald B. Cleaver, Cornell University Library (2015), The Cosmic Microwave Background Radiation Power Spectrum as a Random Bit Generator for Symmetric and Asymmetric-Key Cryptography</a></li><li>Tony Hey, Patrick Walters, Cambridge University Press (1987), The Quantum Universe</li><li>Alastair I. M. Rae, Taylor &amp; Francis Group (2008), Quantum Mechanics (5th Ed)</li><li><a href="https://en.wikipedia.org/wiki/Copenhagen_interpretation#cite_note-56">Wikipedia (2018), Copenhagen interpretation</a></li><li>Eleanor Riefffel, Wolfgang Polak, Massachusetts Institute of Technology (2011), Quantum Computing: A Gentle Introduction</li><li><a href="https://arxiv.org/pdf/quant-ph/0011013.pdf">Artur Ekert, Patrick Hayden, Hitoshi Inamori, University of Oxford (2008), Basic concepts in quantum computation</a></li><li><a href="http://www.damtp.cam.ac.uk/user/db275/concepts/Concepts.pdf">Daniel Baumann, University of Cambridge (2013), Concepts in Theoretical Physics</a></li><li><a href="https://www.exploringbinary.com/number-of-bits-in-a-decimal-integer/">Rick Regan, Exploring Binary (2012), Number of Bits in a Decimal Integer</a></li><li><a href="http://dimitri.xyz/random-ints-from-random-bits/">Dimitri DeFigueiredo Ph.D (2017), Generating random integers from random bytes</a></li></ol><p><em>Originally published at </em><a href="https://blog.red-badger.com/2018/9/24/generate-true-random-numbers-with-a-quantum-computer"><em>https://blog.red-badger.com</em></a><em> on October 15, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8f3f04f09f0c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/red-badger-thinks/programming-a-quantum-computer-generating-true-random-numbers-8f3f04f09f0c">Programming a quantum computer: generating true random numbers</a> was originally published in <a href="https://medium.com/red-badger-thinks">Red Badger thinks</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[React Native: A Checkbox Story]]></title>
            <link>https://medium.com/red-badger-thinks/react-native-a-checkbox-story-17e7ce09db40?source=rss-2cc5610543dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/17e7ce09db40</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[redbadger]]></category>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[Red Badger]]></dc:creator>
            <pubDate>Fri, 17 Aug 2018 14:15:47 GMT</pubDate>
            <atom:updated>2019-06-13T13:37:44.087Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-3beMIQkVbLDxdIE.jpg" /></figure><p>In a recent <a href="https://red-badger.com/blog/2018/6/28/pride-in-london-going-native">blog</a>, we described how we <a href="https://lp.red-badger.com/why-react-native-was-the-solution-for-pride-in-londons-2018-app">built the app for Pride in London</a> with React Native. We mentioned how important accessibility was and that it provided some new challenges. I want to describe one example in more detail: checkboxes.</p><h3><strong>Semantics</strong></h3><p>I should start by saying that, <a href="https://developer.mozilla.org/en-US/docs/Learn/Accessibility/HTML#HTML_and_accessibility">similar to the web</a>, widgets in mobile apps need to be declared with the correct semantics to be picked up by assistive technologies like screen readers. If something looks like a button, sighted users will press it. But if it is not declared as a button, screen reader users will not know that they can press it. In the same way, we need to declare headings, text boxes and also checkboxes.</p><p>React Native supports these semantics by using the properties <a href="http://facebook.github.io/react-native/docs/accessibility.html#accessibilitytraits-ios">accessibilityTraits</a> on iOS and <a href="http://facebook.github.io/react-native/docs/accessibility.html#accessibilitycomponenttype-android">accessibilityComponentType</a> on Android. Looking at the documentation you will notice that there are very few options for Android. This is an area that we should improve. Checkboxes however, are fine on both platforms:</p><ul><li>iOS: Add the trait “selected” when the checkbox is selected; otherwise remove it. Some apps also use the “button” trait to indicate that the element is clickable.</li><li>Android: Toggle between “radiobutton_checked” and “radiobutton_unchecked”.</li></ul><h3>A simple checkbox</h3><p>When we combine the semantics for Android and iOS, add some text and a checkbox image, a simple component can look like this:</p><pre>class MyCheckbox extends React.PureComponent { render() { const { label, checked, onChange } = this.props; return ( &lt;TouchableOpacity accessibilityComponentType={ checked ? &quot;radiobutton_checked&quot; : &quot;radiobutton_unchecked&quot; } accessibilityTraits={ checked ? [&quot;button&quot;, &quot;selected&quot;] : [&quot;button&quot;] } onPress={onChange} &gt; &lt;Image source={checked ? checkboxChecked : checkboxUnchecked} /&gt; &lt;Text&gt;{label}&lt;/Text&gt; &lt;/TouchableOpacity&gt; ); } }</pre><p>In “onChange” we expect the consumer of this component to toggle the checked prop. Using VoiceOver with this checkbox we can hear it saying:</p><p>Your browser does not support the audio element.</p><ul><li>Focus unchecked checkbox: LABEL, “button”</li><li>Then double tap to toggle: “selected”, LABEL</li></ul><p>Your browser does not support the audio element.</p><ul><li>Focus checked checkbox: “selected”, LABEL, “button”</li><li>Then double tap to toggle: LABEL</li></ul><h3>The challenge</h3><p>In the <a href="https://prideinlondon.org/news/pride-in-london-app">Pride in London app</a>, we used a component like this for quite some time. At some point, however, we noticed that VoiceOver was a bit off. When toggling the checkbox, it first read the old state and then the new one as if it was a new component:</p><p>Your browser does not support the audio element.</p><ul><li>Focus unchecked checkbox: LABEL, “button”</li><li>Then double tap to toggle: LABEL, “selected”, LABEL, “button”</li></ul><p>Your browser does not support the audio element.</p><ul><li>Focus checked checkbox: “selected”, LABEL, “button”</li><li>Then double tap to toggle: “selected”, LABEL, LABEL, “button”</li></ul><p>We came up with these points contributing to this problem:</p><ul><li>On double tap VoiceOver always reads the content of the currently focused element.</li><li>Rerendering our components in JavaScript took longer as the app got more complex.</li></ul><p>Together this seems to confuse VoiceOver, leading to a decreased experience for our users.</p><p>TalkBack on Android does not suffer from this problem. The reason might be, that TalkBack does not read out elements on double tab. Instead it requires custom logic to notify TalkBack about the changed state of our checkbox. You can find a good example for this in the <a href="http://facebook.github.io/react-native/docs/accessibility.html#sending-accessibility-events-android">React Native documentation</a>.</p><h3>The solution</h3><p>Since we introduced the issue by increasing our render time, the obvious solution would be to reduce the time we spend rendering. This proved to be difficult, though. We could reproduce the issue sometimes, even if our rendering finished within ~50ms, an acceptable value after a user interaction.</p><p>Instead, we turned to the native side and toggled the “selected” accessibility trait immediately after a tap.</p><pre>- (void) handleTap:(UITapGestureRecognizer *)recognizer { UIView *view = recognizer.view; UIAccessibilityTraits newTraits = view.accessibilityTraits^UIAccessibilityTraitSelected; view.accessibilityTraits = newTraits; }</pre><p>This gives our checkbox the same restrictions as the “ <a href="https://facebook.github.io/react-native/docs/switch.html">Switch</a>” component: it is not possible to cancel the toggle. But it ensures, that VoiceOver always correctly identifies the changed checkbox state, which leads to a good experience for screen reader users.</p><h3>Final words</h3><p>It is important to make sure your app works for everyone. We found, that you to constantly need test your app to make sure you don’t accidentally regress. React Native provides some unique challenges because you need to think about different platforms when building accessible components.</p><p>We published our solution as <a href="https://github.com/frigus02/react-native-accessible-selectable">react-native-accessible-selectable on GitHub</a>. If you experience similar issues, we hope this can help.</p><p>Do you want to give feedback or discuss anything in this article? Tweet me directly here: <a href="https://twitter.com/frigus02">@frigus02</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/921/0*5ePaG4kKlA13k_vg.jpg" /></figure><p><em>Originally published at </em><a href="https://blog.red-badger.com/2018/8/6/react-native-a-checkbox-story"><em>https://blog.red-badger.com</em></a><em> on August 17, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=17e7ce09db40" width="1" height="1" alt=""><hr><p><a href="https://medium.com/red-badger-thinks/react-native-a-checkbox-story-17e7ce09db40">React Native: A Checkbox Story</a> was originally published in <a href="https://medium.com/red-badger-thinks">Red Badger thinks</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Automate non-functional tests with Puppeteer and Lighthouse]]></title>
            <link>https://medium.com/red-badger-thinks/automate-non-functional-tests-with-puppeteer-and-lighthouse-d6a4f71c0d75?source=rss-2cc5610543dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/d6a4f71c0d75</guid>
            <category><![CDATA[lighthouse]]></category>
            <category><![CDATA[puppeteer]]></category>
            <category><![CDATA[redbadger]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Red Badger]]></dc:creator>
            <pubDate>Mon, 13 Aug 2018 11:27:52 GMT</pubDate>
            <atom:updated>2019-06-13T13:42:58.945Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NVvXa36u6zUl3YFd.jpg" /></figure><p>Non-functional requirements, such as page load speed, accessibility and search engine optimisation are often tested towards the end of a project. We know this to be an outdated approach, but the reality is, running a full suite of these types tests on a daily basis would be far too time-consuming.</p><p>Traditionally, an accessibility test would involve a tester manually executing an audit and interpreting the results, sometimes with little acceptance criteria. These audits, useful as they can be, are often reactive in nature and the outcome usually consists of firefighting a range of uncovered issues. Until now, it has been difficult to prevent non-functional issues from being introduced into a codebase by way of automation. This may be about to change though.</p><p>Google have released a couple of impressive tools recently; Puppeteer and Lighthouse. These have the potential to change the way web applications are tested for the better.</p><p><a href="https://github.com/GoogleChrome/puppeteer">Puppeteer</a> is an automation tool for driving tests headlessly through Chrome. The way in which these tests are driven through the DevTools Protocol provides access to the inner workings of the browser and all network requests. The benefit of this is a level of speed and stability rarely seen in UI automation. We’ve trialled Puppeteer within Red Badger and have liked what we’ve seen a lot so far.</p><p><a href="https://github.com/GoogleChrome/lighthouse">Lighthouse</a> is an open source auditing tool that provides feedback on a page’s performance, accessibility, SEO and usability amongst other things. Lighthouse runs the test under conditions similar to those a user would experience in the real world, by throttling the network connection and emulating mobile device usage. In isolation, this tool is extremely powerful and a big step forward in the testing space, providing useful feedback via an easy to read report. The real power, however, comes from integrating with Puppeteer, along with the assertion library Jest.</p><p>By integrating these tools, a development team can run a suite of non-functional tests against their site as regularly as they would any other type of test, even in the CI pipeline. A tester can set the boundaries that determine whether a test passes or fails and act upon an issue the minute it arises. For example, if you value a high level of accessibility on your site, you can set a high benchmark score to reflect this. It’s a huge timesaver to know that you are maintaining a predetermined level in these areas and reassuring to know that any deviations from these levels will be flagged as a failing test.</p><p>An example test to verify that the page load speed of the site meets the acceptable level:</p><pre>it(&#39;passes the set threshold for page load speed&#39;, async () =&gt; { const pageSpeedScore = await commonMethods.getLighthouseResult(lhr, &#39;pageSpeed&#39;); expect(pageSpeedScore).toBeGreaterThanOrEqual(75); });</pre><p>If you like the sound of this and are keen to give it a try, we have created an<a href="https://github.com/redbadger/Puppeteer-lighthouse-jest"> open source repository to get you started</a>. This basic suite of tests will verify a range of properties of a site, from its page load speed to whether it can be deemed a progressive web app. For the most part, we have focussed on validating the accessibility of the chosen site, measuring the colour contrast and presence of alt-text throughout the page, amongst other properties. These are more granular measurements within the area of accessibility, but the same could be achieved within any area covered by Lighthouse.</p><p>It’s important to note that the Pass/Fail thresholds set in this suite are placeholders only. Each of these values should be updated to a score that reflects the teams’ agreed targets. The value of these tests will only be realised when the benchmark figures are agreed upon as a team. More information on the scoring system used in Lighthouse can be found<a href="https://developers.google.com/web/tools/lighthouse/v3/scoring"> here</a></p><p>We’re keen to see how you build upon this suite, so please feel free to fork and share your code and ideas with us @OnionTerror85 or @redbadgerteam. Feedback and comments are always welcome too.</p><p>We’re always on the lookout for prospective Badgers, so if you like the look of us, we’d love to hear from you. All our current vacancies can be found <a href="https://red-badger.com/jobs">here</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/718/0*GEl3rVSxYDX2QGhm.jpg" /></figure><p><em>Originally published at </em><a href="https://blog.red-badger.com/2018/7/23/automate-non-functional-tests-with-puppeteer-and-lighthouse"><em>https://blog.red-badger.com</em></a><em> on August 13, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d6a4f71c0d75" width="1" height="1" alt=""><hr><p><a href="https://medium.com/red-badger-thinks/automate-non-functional-tests-with-puppeteer-and-lighthouse-d6a4f71c0d75">Automate non-functional tests with Puppeteer and Lighthouse</a> was originally published in <a href="https://medium.com/red-badger-thinks">Red Badger thinks</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Automating tasks and tests with Headless Browser Testing]]></title>
            <link>https://medium.com/red-badger-thinks/automating-tasks-and-tests-with-headless-browser-testing-6d4a4501807?source=rss-2cc5610543dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/6d4a4501807</guid>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[headless-browser]]></category>
            <category><![CDATA[test]]></category>
            <dc:creator><![CDATA[Red Badger]]></dc:creator>
            <pubDate>Tue, 24 Jul 2018 12:00:00 GMT</pubDate>
            <atom:updated>2019-06-13T16:39:05.374Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8iCI3i47WtsNFnGH.jpg" /></figure><p>Headless Browser Testing is a way to run a browser in a headless environment. Essentially, running Chrome without chrome! It brings all modern web platform features provided by Chromium and the Blink rendering engine to the command line. Other browsers have followed suit, with Firefox now offering a headless mode as well.</p><p>It’s important as it helps to catch issues, which are not easily reproducible in unit tests. These can range from security related issues like CORS to web platform feature support.</p><p>Historically, automated browser testing has been hard. The standard solution has been to run Selenium, either singly or within a distributed grid. Selenium brings a common protocol to run the same tests in different browsers — even on remote servers.</p><p><strong>But running real browsers comes with a cost:</strong></p><ul><li>The browser startup is slow.</li><li>To run the tests on CI servers you need additional configuration for a display server.</li></ul><p>To get around these issues we have often used a headless browser like PhantomJS instead. This is nice, because it starts faster and works on CI environments without further configuration.</p><p><strong>However, it comes with other issues:</strong></p><ul><li>The browser is not up to date and does not support the latest web platform features.</li><li>People don’t actually use this browser, so their experience might differ slightly.</li></ul><p>The good news is, that both Chrome and Firefox have recently added support for a native headless mode. This means you can easily get real browsers running with fast browser startup and zero CI configuration.</p><p><strong>In addition we see browsers and the community developing features and tools around headless mode:</strong></p><p>* Chrome and Firefox allow to take screenshots of a webpage from command line.<br>* <a href="https://github.com/GoogleChrome/puppeteer">Puppeteer</a> is a very easy to use Node.js library to control headless Chrome.<br>* <a href="https://github.com/GoogleChrome/rendertron">Rendertron</a> uses a headless Chrome inside Docker to provide a rendering API for modern websites. It can be used to enable server side rendering for progressive web apps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/921/0*o-HAOCtKQdpgQOTE.jpg" /></figure><p><em>Originally published at </em><a href="https://blog.red-badger.com/2018/7/23/automating-tasks-and-tests-with-headless-browser-testing"><em>https://blog.red-badger.com</em></a><em> on July 24, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6d4a4501807" width="1" height="1" alt=""><hr><p><a href="https://medium.com/red-badger-thinks/automating-tasks-and-tests-with-headless-browser-testing-6d4a4501807">Automating tasks and tests with Headless Browser Testing</a> was originally published in <a href="https://medium.com/red-badger-thinks">Red Badger thinks</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[User Centred Problem Solving with Anthony Nolan]]></title>
            <link>https://medium.com/@redbadgerteam/user-centred-problem-solving-with-anthony-nolan-5d3bf71ccdb4?source=rss-2cc5610543dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/5d3bf71ccdb4</guid>
            <category><![CDATA[ux-and-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[anthony-nolan]]></category>
            <category><![CDATA[strategy]]></category>
            <dc:creator><![CDATA[Red Badger]]></dc:creator>
            <pubDate>Thu, 19 Jul 2018 14:01:37 GMT</pubDate>
            <atom:updated>2019-06-17T10:10:40.697Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*93Dxvs5mMxEwmQw6.jpg" /></figure><p>Red Badger’s <a href="https://red-badger.com/blog/2017/5/8/lets-talk-about-creating-social-value-honestly?rq=social%20value">social value taskforce</a> started a dialogue with <a href="https://www.anthonynolan.org/">Anthony Nolan</a>, the biggest blood cancer charity. They help save the lives of people with blood cancer and blood disorders with the help of matching stem cell donors &amp; supporters. <br><a href="https://www.linkedin.com/in/jamessmall/">James Small</a>, who is Head of Digital Engagement, got in touch with us and asked if we could run a training session to help the organisation adopt a more human-centric approach.</p><p>A challenge we wanted to address was to make the learning stick beyond the boundaries of the training, make it relevant and easily transferable into the day-to-day work of the team. To achieve this we decided to bring real patients and donors with their experiences into a two-day workshop. Any insights from the interviews, the stakeholder maps, personas, and journey maps would guide the first steps towards a more user-centred organisation.</p><p>Soon <a href="https://red-badger.com/people/clementine-brown/">Clementine</a> and <a href="https://red-badger.com/people/andreas-conradi/">Andreas</a> met James and the department leads and mapped critical touchpoints with patients, donors, medical staff and other stakeholder. Each department lead talked us through the central customer journey and typical pain-points. The complexity of the selected training topic should be high enough to be relevant, and easy enough to give the participants a successful experience in the learning context. Together we chose two user journeys to focus on and James recruited users for the training workshops.</p><p>We ran a two-day workshop for Anthony Nolan to introduce teams to user centred problem solving and had lots of fun. The workshop was attended by representatives from different areas of the Anthony Nolan charity, from Technology to Social Media, they formed a group of around 20.</p><p><a href="https://red-badger.com/people/jun-taoka/">Jun</a>, <a href="https://red-badger.com/people/sari-griffiths/">Sari</a>, <a href="https://red-badger.com/people/steve-cottle/">Steve</a> and <a href="https://red-badger.com/blog/?author=575aba32dfa21e179585df79">I</a> lead the workshop and after a brief introduction we began by splitting the groups in two, each group focusing on a different user journey, one patient and one donor. We invited a volunteer from each to join us for a few hours during the research phase where they shared their experiences with their group.</p><p>We used the <a href="https://www.designcouncil.org.uk/news-opinion/design-process-what-double-diamond">Design Council’s double diamond</a> to structure the workshops.</p><h3>Day one: First diamond</h3><p><strong>Discovery</strong><br>We kicked off with discovery.</p><p>Challenges Anthony Nolan faced, from donor acquisition to communications and measures of success. Followed by user needs, for which we had arranged a donor and patient to come along and speak about their end to end experience with Anthony Nolan. From how they came across to finding out about Anthony Nolan, all the way through their experience as a donor or a patient. For some it was the first time they had spoken to a donor or a patient and it was an eye-opening experience for them. The interviews conducted by the Anthony Nolan teams were a great place to start identifying problem areas and opportunities to improve.</p><p><strong>Define</strong><br>To bring the insights from the interviews to life, we built customer journey maps. This allowed the teams to understand the whole Anthony Nolan journey from the perspective of an end user. It was a great exercise thinking about the different touchpoints users experience under the same brand, that is Anthony Nolan.</p><p>We finished the day by defining the problem statement from the obvious pain points on the user’s journey and generated <a href="https://designsprintkit.withgoogle.com/methods/understand/hmw-directions/">How Might We</a> questions to help fuel us on building ideas.</p><h3>Day two: Second diamond</h3><p><strong>Develop</strong><br>We kicked off the second day with some rapid idea generation. A few rounds of quick sketching with Crazy8’s and the teams picked an idea they wanted to develop further.</p><p>This part was quite fun (and challenging) as the balance of crazy ideas to the realism of feasibility is a fine line and a learnt skill.</p><p>“I can’t draw” was no excuse, and even the team members who were reluctant at first got into drawing loads of ideas.</p><p>By the end of the sketching sessions, we had lots of great ideas. To help prioritise which idea to try out first, we mapped them on <a href="https://red-badger.com/blog/2017/7/4/enter-the-matrix-lean-prioritisation?rq=lean%20prioritisation">a grid of effort to implement vs user value</a>. Visualising the ideas based on the two criteria helped teams pick the one they’d want to learn from quickest; which were the ones that would take low effort to implement while delivering high value to end users.</p><p><strong>Deliver</strong><br>Once the teams had chosen the idea they wanted to take forward, we moved on to delivery — which is all about prototyping and quick learnings.</p><p>The biggest learning we wanted to come across was the non-attachment to ideas and prototypes. To visualise the winning concept to the teams’ chosen problem statement we made a poster.</p><p>The goal of the poster was to introduce testing ideas early on and to emphasise the importance of having a clear value proposition. Each team made a poster and received feedback on the presentation of their concept which they used to refine for the next activities.</p><p>After the teams had the concept ready to go, we brought the prototyping boxes out.</p><p>If you haven’t heard of it before it is the box every kindergarten has and every adult dreams of getting their hands on. These boxes were full of stickers, cardboard pieces, and all the craft materials you can think of. The materials aim to replace overthinking of the perfect solution and focusing on the message — while having fun.</p><p>Some even went “outside the box” and used the coat rail that was in the room.</p><p>We ended up with amazing prototypes that were simulating their solution to the pain point they had identified. All in just two days.</p><p>We had two judges, <a href="https://red-badger.com/people/nathalie-goepel/">Nathalie</a> and <a href="https://red-badger.com/people/claire-murray/">Claire</a>, on the day that would participate and award the teams based on their prototypes.</p><p>The awards were:</p><ul><li>Content King</li><li>Fancy Pants</li><li>The craft experts</li><li>The best wizards</li></ul><h3>Learnings and all the fun</h3><p>All in all it was a great two day experience with such an enthusiastic crowd.<br>We had loads of fun and were very proud with the ideas and prototypes the teams put forward.</p><p>Here’s what the participants had to say about the two days:</p><blockquote><em>“I enjoyed the two days and working through the process. It was good to do something so activity focused and learn by doing.”</em></blockquote><blockquote><em>“I learnt … How to test ideas quickly and easily through prototyping”</em></blockquote><blockquote><em>“The most valuable piece of information I learnt was … to try something small and then build on it — don’t need to go out with something perfect.”</em></blockquote><blockquote><em>“Red Badger put together an incredibly thoughtful workshop that was completely tailored to Anthony Nolan’s needs. All our participants left raving about the new techniques they’d learned, and the valuable insights and perspectives they’d gained from talking to our donors and patients. We have definitely become more focussed on user needs as a result of the workshop, and we have established a shared language, so most people understand when we talk about user-centred practice that we’re not talking about a technical methodology that lives in the Digital team but rather about something that goes to the core of our organisational values. We have also taken away lots of practical techniques for rapid idea generation and prototyping, which we’ve applied successfully to projects already.”</em></blockquote><p>It’s best to do User Centred Design by doing. Seeing the mindset shift, even slightly was very rewarding. At the beginning of the two days, Anthony Nolan teams knew they had to shift the focus to their end users but didn’t know how. They had been talking and planning about solutions that didn’t go anywhere. Wanting to come up with the perfect solution on the first time around can be a blocker to getting ideas off the ground. The two days gave Anthony Nolan a space to listen to users, explore even the craziest ideas and test them out with the permission to fail.</p><p>The two days gave them the inspiration and hopefully a user first mindset and that they can now carry on in their day to day work.</p><p>Not long after the workshop we got great news, the graduates of the training had already started implementing their learnings at Anthony Nolan. They had run a Crazy 8’s and a How Might We session to explore ways of transferring their User Centred Design skills across the business and are including more learnings in their day-to-day work.</p><p>Here’s what they will be working on internally:<br>“HMW disseminate what we’ve learned about UCD among our teams and others?”<br>“HMW embed a user-centred culture at Anthony Nolan?”</p><p>We are very proud and can’t wait to see the outcomes!</p><p>Want to get a bit more insight into the workshop? Check out some more photos of the two days on our facebook page <a href="https://business.facebook.com/pg/RedBadger/photos/?tab=album&amp;album_id=1970964912923242">here</a>.</p><p>If you’d like to discuss running a UCD training with your team, get in touch at <a href="/service/mailto:hello@red-badger.com">hello@red-badger.com</a></p><p><em>Originally published at </em><a href="https://blog.red-badger.com/2018/7/4/user-centred-problem-solving-with-anthony-nolan"><em>https://blog.red-badger.com</em></a><em> on July 19, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d3bf71ccdb4" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>