Tag: Design Thinking

  • Systems thinking for DesignOps

    If DesignOps is about designing processes and defining transformative strategies, it is important to apply a Systems Thinking approach to ensure the strategy delivers on the expectations and does not move inefficiencies across the organisation.

    Systems Thinking is a holistic critical thinking approach that focuses on the analysis of the relationships between the system’s parts to fully assess the context (more here). By understanding how every part of the system is interconnected to the others and by evaluating how a change to one part affects the dynamics and relationships of the whole system, System Thinking becomes a powerful approach to decision making and change management to maximise impact and minimise risks.

    System Thinking sees the organisation as an integrated, complex composition of many interconnected systems, both human and non-human: all these components need to work together and cooperate effectively to empower the whole (the system) to function efficiently.

    If the organisation is a system made by smaller units, then a system can be broken down into discrete sub-units. These sub-systems need to interact together and cooperate effectively on an ongoing basis to empower the system to accomplish its purpose. 
    Form an organisational point of view the major sub-systems are:
    – People
    – Processes
    – Technology and tools
    – Resources

    And each of these sub-systems can be broken down into more sub-systems: by exploring and expanding the systems, the overlaps and the interconnectedness among the parts become visible, showing how every part is deeply interwoven to the other units of the system:

    The organisation as a System is made by a number of subsystems that compose a complex system of relationships and interdependencies.
    The organisation as a System and an example of sub-systems.

    The division in sub-systems shows a complex web of relationships among all parts and when the system’s analysis is done to a granular level, it becomes clear how a change to any part drives potential alterations to other parts. Moreover, in the model some sub-systems are closer and embedded with multiple sub-systems: i.e., although HR is a process focused function, HR touches deeply sub-systems such as People and Resources too.

    It is important to highlight that in a systemic approach there is no single way of categorising and organising the systems: each system is unique and each variable or prioritisation criteria adopted, if appropriately exploited to identify the relationships among the parts, will provide an in depth view of the context and the relationships.

    Why does Systems Thinking matter for DesignOps?

    If DesignOps is a transformative function that drives transformational initiatives to maximise value creation to multiple stakeholders by optimising and improving processes, ways of working, and engagement models, then the impact of every transformational act transcends Design and touches a number of relationships across the system.

    The same change management approach that enables DesignOps to carry out value driven transformational initiatives needs to be coupled with a systemic approach to fully understand the benefits and extended impacts of any DesignOps’ initiative. 
    The systemic approach becomes critical because DesignOps delivers business impact on multiple levels — speed to delivery, quality of output, time to market, spending efficiencies, increased ROI… — to multiple stakeholders, from the designers to the cross-functional partners, making DesignOps a systemic discipline. Moreover, Design’s positioning as a cross-functional and collaborative discipline that relies on ongoing relationships with other non-design partners reinforces the systemic nature of DesignOps and the needs to include Systems Thinking among the success criteria of any transformational initiative.

    If DesignOps’ focus is to improve operational and spending efficiencies and to maximise value creation, DesignOps needs to understand the inter-relations and the deep connections among the parts of the system to exploit those relationships to enable benefits to propagate within the sub-systems and the organisation.

    Where does DesignOps stands in a systemic view?

    DesignOps operates at the heart of the Design sub-system and DesignOps itself is simultaneously both a system and a sub-system, because it is both influenced and it influences a number of relationships on multiple levels.
    For this reason, DesignOps operates simultaneously both inside-out(from the design teams to the organisation) and outside-in (from the broader organisational level to design).

    The model below shows how and where DesignOps operates at a systemic level, providing a simplified view of the different levels and diverse relationships that are touched by DesignOps.

    From a Systemic view, the organisation is divided in subsystems: the business units, the teams of each Business Unit, the focus of each teams, the areas of intervention of each team. Every action taken in any area impacts the system.
    A simplified systemic view of DesignOps’ placement in an organisational systemic view.

    The image shows different levels of sub-systems, from the macro-level of the organisation and the Business Units, to the micr — level, the specific teams’ engagement model or resource.
    It becomes then clear that an action at a lower and more granular level, like introducing a new design tool can have a broader impact beyond the design teams and it can influence engagement models, processes, and collaboration both with designers and with the cross-functional partners, ultimately impacting the organisation as a whole.

    How does System Thinking work for DesignOps?

    The focus of DesignOps is to create operational and spending efficiencies for the Design teams by re-designing and optimising the existing operational frameworks on multiple levels to create value to both design leaders, designers, and the organisation.

    If the organisation is the system, then by creating value to the organisation, DesignOps potentially touches all other sub-system pertaining to the main system that have both a direct and indirect relationship with Design.

    Every single sub-system can be touched by changes happening within the Design teams: If DesignOps changes one aspect of the E2E design process, such as adding a new prioritisation process, this new process can impact cross functional engagement models, changing how teams and team members interact. And this change can also drive new needs for tools or resources that will move from Design to other parts of the organisation, such as finance or other leaders.

    By transforming the teams operational models to improve efficiencies, those same efficiency-driven initiatives can impact and propagate across different teams and sub-systems within the organisation. Therefore being able to apply a Systems Thinking approach to assess both the immediate, medium and long term potential consequences of change becomes a critical skills that enabled DesignOps to maximise impact on multiple sub-systems.

    It’s the intrinsic collaborative nature of Design that calls for a systemic approach and this approach can unveil any potential silos or unexplored relationships within the system (the organisation).

    The best tool to assess the impact of changes are Scenarios: scenarios are a path through the system to explore one or multiple flows and to analyse the impacts of possible future events on the system performance by considering diverse alternative outcomes.

    Scenario Analysis are used in Systems Thinking to probe how any change influences the systems and sub-systems. Scenarios explore potential use cases of all possible implications looking at the impact on relationships and exploring consequences on people, processes, and business. 
    Scenarios lead the definition and assessment of any potential outcome that may emerge from a change in one part of the system through a set of probing questions to evaluate the systemic impact. Some obvious questions that can drive the definition of the scenario may be: 
    – How would this change propagate through the system?
    – Which are the sub-systems affected? 
    – How and when would the sub-systems experience the impact of the change?
    – How would people outside design / the current sub-system react to the change? (assuming a participative change management has been applied to define the solution)
    – Which of the existing frameworks and ways of working may be directly and indirectly affected by this change?
    – What are the consequences on the ways of working and collaboration?

    To effectively exploit the power of scenarios it can be important to have clear metrics from the experiments and from the DesignOps’ approach as described here: measurements and a baseline help defining the potential impact on various dimensions (Time, Quality, Resources) and by probing how the system would respond to a propagation of new initiatives, a scenario would provide an outlook of future possible downsides or opportunities. By quantifying potential positive and negative impact through scenarios DesignOps can therefore assess impact and the value of the transformation across all teams and sub-systems.

    A practical Example

    When assessing the importance to introduce a research recruiter service to help the design teams to work faster and smarter, the initial efficiencies were focused on Design teams. It was clear that there were major inefficiencies stemming from the Design teams, whose economic impact was over $500,000 / year with a significant burden on teams’ life/work balance.

    So the solution had to focus on Design teams’ operational capacity to impact financial perfomance but it also could influence the organisation as a whole to maximise ROI and to open additional opportunities to non-design teams.

    So if the explored solution was to introduce a new role, a Research recruiter that would handle all participant sourcing needs, what would that mean for the system and sub-systems?

    Assessing the potential impact of an action means creating hypothesis and attributing credible and achievable success metrics that provide an assessment of the potential impact across the organisation by looking first at the direct impact on Design teams, such as:

    • Reduce lead time to recruit (-20%)
    • Reduce costs (-25%)
    • Increase number and variety of research participants (+35%)
    • Increase quantity of test, making testing easy (+30%)
    • Save designers’ time! (-25%)

    Some of these metrics, such as saving Designers’ time would also impact other subsystems, such as life/work balance, which would impact churn…

    After the definition of possible quantifiable metrics for the Design teams, it is important to assess the consequences for the non-design teams:

    • Increase number of user engagement and research sessions for all Business Units and teams (+50%)
    • Improving spending efficiency for the organisation (-35%)
    • Increase ROI of engagements with users by multiplying engagement per session
    • Creating opportunities to join research sessions through cross-functional visibility of research initiatives
    • Increase organisation’s empathy and understanding of the user

    Knowing how change propagates through the systems at all the levels is essential to plan and execute the change beyond Design.
     
    Scenarios were used to define the business case and to stress test the systemic impact on the organisation. Scenarios were also key to set the expectations and define what were the expected and the extended benefits be for the system of the suggested solution.

    DesignOps needs a System Thinking approach as by improving the engagement models, the tools, the processes, and the operation of one team, DesignOps implicitly touches also other teams because ways of working are all collaborative and strongly intertwined and the very nature of DesignOps is systemic and transformational.

    The UX Collective donates US$1 for each article published on our platform. This story contributed to Bay Area Black Designers: a professional development community for Black people who are digital designers and researchers in the San Francisco Bay Area. By joining together in community, members share inspiration, connection, peer mentorship, professional development, resources, feedback, support, and resilience. Silence against systemic racism is not an option. Build the design community you believe in.
  • Adding change management to your DesignOps’ strategy

    DesignOps is a transformative function that focuses on the very heart of the teams’ operative system. For this reason, a participative approach to change management is key to ensure success and impact. Yet, the importance of change management as a core skill is still often overlooked.

    A successful DesignOps initiative is a transformational act that delivers value to the teams, the leaders, and the organisation by optimising and improving processes, ways of working, engagement models, and tools ecosystems. 
    As a process and inward-looking discipline (see here) DesignOps works on the core operational structures that enable relationships, workflows, optimisations, and efficiencies. And to achieve the expected results, DesignOps needs to effectively orchestrate actions across all cross functional and design teams and this is why DesignOps’ success heavily depends on how well the change and the transformation are managed.

    Design Thinking as DesignOps’ foundational approach

    DesignOps is a discipline that builds and benefits from a solid Design Thinking process to enable operational changes.
    DesignOps’ Design Thinking approach is not only a strong and necessary legacy, but it is the most powerful method to fully understand the problem and the users, to explore and experiment with solutions to ensure that there are tangible and measurable improvements and the changes introduced are durable and consistent with the context and processes.

    This is the classic double diamond approach that is equally effective both for Design and for DesignOps initiatives:

    Double Diamond Design approach

    But when the users are your own teams, Design Thinking’s dynamics and the expected impact change, as the final solution should be a durable change in the existing process and in the current designers’ experience.
    Design Thinking is a process for creative problem solving (IDEO), its focus is the final output (the solution), but DesignOps needs to ensure that the solution transforms processes to maximise benefits on the long term.

    DesignOps focus is not on the output — the actions needed to deliver results os the final deliverables— but on the the outcome and the impact, the tangible and intangible benefits resulting from the project activities.

    This is why while Design Thinking is essential to explore the problem and opportunity space to test and define the most effective option, however DesignThinking by itself cannot deliver durable changes that scale benefits and deliver the business goals and efficiencies on the long term.

    Understanding Change management: Lewin’s Model

    Organisational change refers to all initiatives that affect any of the organisation’s core operational structures, such as tools, culture, processes, ways of working. Managing this change — change management — is the approach required to ensure that new processes, new ways of working, and new engagement models are actually adopted by the people who are affected to ensure they deliver benefits on the long term (more here and here).

    DesignOps operates at the very heart of the design teams’ operative system to deliver value and to bring tangible and quantifiable improvements to both design teams and the organisation.

    This is why DesignOps needs to combine a Design Thinking approach with a well defined change management strategy to ensure full buy-in and engagement from all who are affected by the forthcoming transformations.

    Although there are many change management models, the original archetype that has given birth to the formalisation of change management as a discipline, is Lewin’s model. This approach was developed in the late ’40s and this 3 steps model is shows the key phases of every change process (more on the model here).

    Lewin’s model describes change as a three stage process, made by the following steps:

    Lewin’s three steps model on Change Management

    Lewin’s model shows the three critical steps and actions required to manage transformative projects and to ensure change is embedded in the organisation and the culture and delivers benefits on the long term.

    DesignOps meets Change Management

    If DesignOps delivers transformational projects to improve the ways teams engage, operate, spend, and work, then DesignOps does need a strong change management approach. 
    This why combining Design Thinking with a change management approach is introduces some minor, yet key, modifications to the classic double diamond model:

    The combination of Lewis’ change model and the double diamond shows 2 key differences: an additional stage to ensure adoption is collectively agreed, and an iteration that is related to teams’ acceptance and not on measurable results.

    The graphic above shows the double diamond framework with a tweak at the end and it combines Design Thinking with Lewin’s 3 stages of change. 
    Lewin’s 3 phases can be aligned with the double diamond model, but being Design Thinking for DesignOps, there are some changes that need to happen to ensure Design Thinking meets change management in a participative way.

    In fact the Unfreeze phase corresponds to Design Thinking’s initial problem setting and empathy driven approach to define the user problem and identify opportunities. This is when issues are revealed and by making problems explicit the process creates awareness and enables the need for change.

    The Hypothesis and Experimentation phase, when the focus is on the solution and the actions is when Change happens and needs to be driven through influencing and engagement strategies to test and experiment changes. This phase is where action happens and where the planning and design of the transformation happens — a transformation that requires engagement, over-communication, and team empowerment.

    The final step, the Freeze stage is where impact is measured and decisions are made. This is where the classic double diamond has a tweak and shows an extra half diamond to ensure the decision is made collectively and change is made sustainable and attainable through trainings and support.

    In a participative approach to change management, compared to the classic Design Thinking model, there are 2 opportunities for iteration based on results and feedback, the second of which is strictly connected with the decision to Freeze.
    If the experiment does not provide objective satisfactory results, the experiment needs to be redesigned and the process needs to look again at the solution ideation phase. This is the Design Thinking loop, where experiments provide measurable results to decide if the solution is worth progressing.

    In a participative approach though, even if the objective results achieved and even if the experiments deliver satisfactory results, if the leaders, teams, stakeholders do not accept to adopt the change in the Decide/Adoption stage, the change is not implemented (frozen) and another iteration of the experiment is required until all those involved in the change agree to adopt the transformation.

    For change to be implemented, transformational initiatives need to achieve both positive objective impact and teams’ acceptance. Without acceptance, no change can succeed on the long term.

    Bringing participation at the heard of DesignOps’ transformations

    For the reason stated above about acceptance, the biggest addition to the classic double diamond is in the highlighted focus on participative elements, formalised in the LISTEN and SHARE activities: ongoing two-ways conversations with design leaders, designers, and cross-functional partners are necessary to ensure DesignOps operates in a transparent and participative manner and all feedbacks and concerns are taken into account in a timely and open way.

    The combination of Design Thinking and change management makes DesignOps a participative user centred transformational approach. By putting the users, the designers and stakeholders, at the centre of the process and by ensuring that all involved are engaged and part of the decisions is key to deliver long lasting benefits and value.

    A case study

    Change requires and takes time, so while the graphic looks straightforward, transformational processes require time and patience. The following example described high-level actions and the rationale of an ongoing experiment.

    Step 1: Unfreeze and understand the problem
    A survey and interviews were run with the teams to understand their biggest pains and what could improve their experience as designers. 
    It emerged that one of the top asks was to learn more: more trainings, more opportunities to be inspired from experts outside the organisaton.

    Step 2: Share and create the need for change
    Learnings form the surveys and interviews were shared with both teams and leaders. Sharing with leaders meant sharing the findings, the analysis, and also providing full transparency and access to the raw data. To establish trust and build the future engagement it is important to act with a full open and transparent policy and provide access to any working material. The ask for raw data generally helps leaders to better understand their teams and it is a way to maximise the impact of any data collection effort.

    Sharing with teams is key to ensure they trust the process and they see the impact and value of their feedback. Designers need to acknowledge that they influence and determine their own ways of working: sharing with the teams is a way to empower and engage everyone.

    Participative and ongoing sharing is a win-win strategy: nothing creates the urge and need for change more than realising that an individual pain is actually a collective shared one.

    Step 3: Change! Making hypotheses and designing experiments.
    After learnings have been shared and discussed, DesignOps needs to do its magic and turn a problem into an opportunity by defining what success looks like and creating hypothesis and experiments.

    How may we foster a learning culture and bring more training opportunities to scale up designers’ skills?

    Again, every solution, idea, option was shared openly: stakeholders needed to commit and agree on the solution, teams had to understand what was happening, and most importantly, why and how they started this transformative initiative with their feedbacks.

    Step 4: Share and learn from comments!
    The planning approach to define what would become a 6 months’ Academy looked at all aspects: trainers and speakers, times that would work for all, time zones coordination, calendar synchronisation… The participative approach consolidated the first experiment: every week, for 6 months, designers would be invited to 60/90 minutes sessions with external subject matter experts.

    Step 5: Testing and measuring
    To be able to test impact, it was necessary to clearly identify which behaviours and parameters the experiment needed to affect. What would success look like for an educational experiment? Designers were invited to complete another survey to assess confidence in key areas the Academy would address. These data created the baseline to assess impact and change in an objective way.

    Step 6: Shall we Freeze? Evaluate and Decide. 
    After 6 months, it was time to collect structured feedback. Teams and leaders were shared comments on an ongoing informal base and it became clear after 3/4 months that there was need to improve some aspects of the experiment. But which aspects were relevant to leaders and which were key for designers?

    Another survey measured the impact on designers’ skills and explored the overall experience to decide if the experiment was the right change and if it was ready to be consolidated or if we had to go back (more on this experiment, here).

    Although the objective impact and the lift in confidence was satisfactory, the feedback from the teams and leaders were against accepting this as a permanent change. This has meant exploiting the elements that have delivered the lift in the objective impact and improving the experiential aspects that made the majority of those involved refuse to adopt the change.

    Everything has been constantly up for reviews and conversations making this a fully Bottom-up transformational initiative, where the initial input was originated by teams and the final validation came from them again.

    Lesson Learnt

    DesignOps is not a top-down approach: delivering transformation requires an approach that is participative in nature, user centred, and inclusive, where everyone’s voice is heard and addressed to ensure transformation is owned by all who are involved.

    Success in DesignOps is never immediate as transformational initiatives may require objective results to be fully aligned with user acceptance and adoption.

    Operational transformations need to be designed and driven with a clear view and an approach that combines seamlessly both the power of Design Thinking and the transformative impact of participative change management.

    The UX Collective donates US$1 for each article published on our platform. This story contributed to Bay Area Black Designers: a professional development community for Black people who are digital designers and researchers in the San Francisco Bay Area. By joining together in community, members share inspiration, connection, peer mentorship, professional development, resources, feedback, support, and resilience. Silence against systemic racism is not an option. Build the design community you believe in.
  • From T-shaped to π-shaped designer

    The role of designers is changing and new approaches are needed to foster a mindset that can support them to become more impact-focused and a key strategic partner. How can DesignOps help driving Designers’ transformation to maximise results and influence?

    A T-Shaped designer had great skills and a focus on execution and delivery. But a π-shaped designer i data driven and focused on impact and collaborative conversations that can drive maximum results.

    Design has gone a long way in the past 10 years thanks to the rise and impact of Design Thinking and to the impact design has had on businesses. There are a number of studies reporting how companies with Design teams have higher profits, such as McKinsey 2018, John Maeda’s Design in Tech Reports, The Forrester Report 2020.

    Yet, many design leaders still complain about the role and positioning of Design within their organisation, claiming that their team is unable to influence conversations and that Design is still expected to execute briefs and deliver pixel-perfect prototypes or designs. But that is only one side of the story, because it is also important to learn what is the experience that engineers, product managers, and marketing teams are having with the design teams to answer the question Are design teams really misunderstood or are they missing an opportunity?

    To answer this question, both the shape of the design teams and designers’ skills matter and influence the positioning of Design.

    We have seen a growth in the so-called T-shaped designers: technically impeccable designers capable of perfectly execute any brief and delivering on time. These are greatly talented and highly skilled professionals, but to fully empower Design to reach the strategic positioning it deserves, they need to learn to collaborate on new grounds and with enhanced approaches with their cross-functional partners to ensure designers are not executing briefs but influencing decisions.

    It is DesignOps’ role to own this issue and to define the strategic approach to understand the root causes of this situation. And this required a deep understanding of what was the current experience that design partners were having with designers. A survey and 1:1 interviews revealed that there were a certain number of recurrent issues that cross-functional partners were experiencing with the design teams, but two were the key issues that were having the biggest impact: designers’ limited decision-making capacity and the design team’s overall reactive attitude.

    Why that? Why these aspects were important and where were these issues coming from?

    From Design Thinking to Data thinking

    Design Thinking has made empathy and user obsession one of the signatures of how design teams operate. Yet Design Thinking’s overall qualitative approach that investigates unmet needs has not been fully expanded towards a stronger formalised data-driven quantitative approach to measure users behaviours and impact.

    In the era of the quantified self, it’s also time to start thinking and embracing the era of the quantified user, and to do so designers need to evolve their approach to new dimensions.

    If Design is about nudging users to adopt better ways to achieve their goals, if it is about creating delight and meaningful experiences, measuring behaviours and quantifying the impact of the experiences that are being delivered is the single most important element to ensure design thinking has the impact it promises in its empathy-led approach. This becomes important because if cross-functional partners are using metrics and KPIs to assess performance and impact, it is hard for designers to compete on the same level when they focus mostly on stories and empathy with no solid data-driven approaches.

    Empathy and narratives are essential to influence, but decisions today are made with data.

    T-shaped designers in our teams were not fully relying on analytics: when in an internal survey and follow up interviews designers were asked about the tools and data points they were using to make decisions, the vast majority admitted not only that they felt they did not know much about analytics, but they were not sure about the tools and resources that were available to them. 
    And although the organisation had 3+ analytics tools available to all in an effort to democratise data, yet many designers felt that analytics was “the analytics guys’ stuff”.

    But having to rely on the analytics’ guys to get behavioural data, also meant that when a designer wanted to check on the performance of an in product feature, these queries had very low priority for the analytics teams, meaning that the data may take days or even weeks to arrive. And of course, these low added value asks from the design teams were not helping the relationship between Design and Analytics.

    This demonstrates the need to rethink designers’ mindset and move from a T-shaped to a π-shaped approach to Design. π-shaped designers combine Design Thinking with a solid data driven approach: they use data to make informed decision and to quantify changes in users’ behaviours. π-shaped designers drive conversations and visions with their cross-functional partners thanks to the shared focus on impact and the ability to use analytics as a common language: in this new approach, data complements and strengthens designers’ deep understanding of the users’ pain-points and supports their capacity to be part of the decisions and to be proactive in identifying impactful opportunities.

    What if we nurture a data-informed mindset?

    These considerations led to an experiment: can we foster, and measure designers’ mindset?

    This type of overarching strategic initiatives fall within DesignOps’ strategic remit. Fostering a data driven mentality, requires an ongoing commitment, time, and support from the leadership and the teams and it needs a combination of both the technical training on existing platforms and ongoing exposure to best practices and case studies.

    DesignOps partnered with the analytics platform suppliers by sharing the concerns, analysing the expertise gaps, discussing the opportunities, and defining a learning plan to increase teams’ understanding of the platforms.
    On the other side, a number of Subject Matter Experts have been invited to share case studies, best practices, examples on how analytics and data can be used in Design and innovation.

    This soon become a 6 months’ initiative: both the technical training on tools and mindset shaping initiatives were needed to ensure designers started asking the right questions and touse tools to answer those questions. 
    Data driven is a mindset that is supported by tools and platforms. The agreed commitment with design leaders and teams was to attend 90 minutes’ sessions 3 times a month. Basically a total of 4.5 hours a month with a weekly commitment.

    The results after 6 months

    Assessing the impact of how training initiative impact teams’ development of a more data informed mindset requires… data!

    For this reason, ahead of the sessions, all designers were asked to fill a skill matrix assessment to understand teams’ strengths and opportunities and to assess the level of confidence in data and in analytics platforms and tools. We also collected analytics data to understand the current engagement and utilisation of the existing data platforms to answer a key question: how much and how often were designers engaging with analytics tools?

    It was important to both understand self-perception and to triangulate that with behaviours to get a full picture of the initial situation and to quantify actions and attitudes.

    All these data point, the behavioural analytics and the skill matrix, were the baseline. 6 months and 30 hours trainings later, designers were asked to fill the same matrix and new data were collected from the platforms to understand if there were any changes in designers’ behaviours.

    Yes, the needle was moving and it was moving in the right direction!

    Designers were asked to rate their confidence in the domains touched by the trainings, and while confidence in data and analytics increased up to 12% with an average increase of 8%, the confidence in using analytics tools and platforms increased by up to 29%!

    Behavioural data from platforms’ analytics confirmed these self-assessments, with an increased engagement that overcome all initial hypothesis: in 6 months there was a 70% uplift in the number of data and analytics projects launched by designers, an 1,800% increase in designers’ queries to the platforms, and a +170% increase in overall engagement with all analytics tools.

    Can we foster and nurture a data-driven mindset?

    Yes, we can. But it takes time: these results are just a starting point: maintaining momentum, ensuring new acquired behaviours become habits, strengthening confidence, and establishing the habit to think and to make decision with data is a mindset that needs to be exercised constantly, like a muscle.

    These initial results can be quickly nullified by the wrong initiatives and it is now key to rethink and to learn from these 6 months to identify opportunities to consolidate the learnings and nurture the mindset.

    Because one positive result is not a victory, it is the beginning of more targeted and efficient actions to increase designers’ engagement and excitement for data and to ensure we foster the π-shaped mentality that can allow Design to move into the strategic and influencing space it deserves.

    The UX Collective donates US$1 for each article published on our platform. This story contributed to Bay Area Black Designers: a professional development community for Black people who are digital designers and researchers in the San Francisco Bay Area. By joining together in community, members share inspiration, connection, peer mentorship, professional development, resources, feedback, support, and resilience. Silence against systemic racism is not an option. Build the design community you believe in.