Blog Layout


How do high functioning agile squads achieve progress? By thinking like a scientist.

Hands up if you work for a large corporate that hasn't shifted at least some of its resource to agile methodology? There's not many - over the last decade there has been a widespread shift across New Zealand organisations to agile. And it makes sense - break work into smaller chunks, deliver more frequently, pivot faster and realise business results sooner.



We've worked in, with and near some of these companies, and have witnessed a variety of results, all coming down to the way squads approached their challenges. After all, agile is just a structure, so what separates high and low functioning teams? One feature we witnessed of the high functioning teams is a curiosity informed by evidence: a scientific mindset.

A focus on the problem, not the solution

In many organisations, agile and non-agile alike, we see people seeking to provide solutions, at the expense of more careful consideration of problem definition or discovery, and with little investment in evaluating the impact of their ideas. 


This often ends up in a 'survival of the fittest' - or at times, survival of the loudest voice in the room. 


Agile done well helps teams focus on resolving a problem, rather than providing a solution. It's a subtle reframe, but an important one. It means working forward: agreeing on what the challenge is that our squad is being formed around; what metrics show us that the problem is there (and that we are potentially impacting it); and being clear about what our assumptions are. 


Squads engaged in this way are focused on learning and understanding what is really driving the challenges they are there to resolve. And it fits really nicely with the scientific approach. 


Getting into the right mindset

A scientific mindset doesn't mean getting out lab coats and chemistry sets. It's about taking the scientific learning process and applying it to your business challenges. 


In Richard Chataway’s book The Behaviour Business: How to apply behavioural science for business success, he points to the role of science in solving mankind’s problems, and how a scientific mindset is underpinning the success of some of the world’s most successful businesses.


“The houses we live in, the food we eat, the transport we use: all of these contain innovations that were developed by scientists using the scientific method. A hypothesis based on scientific evidence, followed by a deduction, and tested through observation. Then repeat. And yet, in business, little work is scientifically based. In fact, most of it involves no experimentation, and an awful lot is based on outdated assumptions. Isn’t it time we remove the guesswork?”


Consider the typical stages of a scientific process:


  1. Define a question to investigate
  2. Create hypothesis
  3. Test with an experiment
  4. Analyse data
  5. Report conclusions


You can see how easily these transfer to a business challenge/project situation:


  1. Turn your challenge into a question to investigate, e.g. "How might we increase the number of customers self-serving online?"
  2. Make observations, collect data, research - talk to actual customers, and don’t forget to review any research (including that conducted outside your organisation) you already have access to.
  3. Create your hypothesis. Remember, this is essentially your educated guess on how to answer your question in step 1. For instance, "Redesigning the self-service menu to highlight the three most common tasks will encourage more customers to trial an online service offering, before resorting to phone"
  4. Put the hypothesis out to experiment. In this scenario, an A|B test could work well, in which half of customers see the existing webpage and half see an updated webpage.
  5. Analyse the results. Did it work? Or did it simply sound like a good idea, that failed to have an impact in the real world?
  6. Review and implement, adapt and re-test, or workshop through the next challenge. E.g. what did we learn? Should we scale up and turn into a BAU proposition? Are there some customer segments that this didn’t work for, and need a different solution?


Delight in being wrong

Of course, testing our concepts can mean we discover they don't work. 


There’s a scientific principle that our theories are never proven to be true, only proven to be wrong. This means it only takes one result to disprove an idea, and that all others are just in a permanent twilight zone waiting to be shown that they are wrong. From a business or design perspective, that probably feels unsatisfactory (or unmotivating and generally depressing!). But from a learning perspective - and when viewing it from a long-term impact perspective - it's actually ideal. 


We want to find out that we're wrong, so that we can more quickly, effectively and cheaply, move onto more effective ideas. It's the ultimate ‘test and learn’. 


There's a certain humility in being guided by the evidence, allowing yourself and your squad to put aside your own ideas and expectations, and accept what emerges from the discovery and testing process. The evidence can come from a range of sources, and some are more rigorous than others. But the key is to rely on the evidence at hand - even when it goes against our pet theories or ideas. 


Try reframing being wrong from a failure (which it's not), to a cause for celebration - the test was successful! And then you can do what all good scientists do: find another question to investigate.


Moving faster … with more curiosity 

Taking on this approach in your squad shouldn't mean you take the fun out of ideation and delivery, it's just about helping you streamline your processes to deliver the right solution, for the right problem. It's up to your squad's experience and judgement to decide where to focus attention and how to apply the findings.


The other benefit is that this process should help your squad move faster, from problem statement, to solution possibilities, to scalable strategies. For teams struggling to get traction it’s a great way to see – and demonstrate – progress, and move past having the same ‘what if’ conversations over and over again.


If you need some help or ideas on applying a scientific mindset to your project or challenge, get in touch.


By Cole Armstrong September 4, 2024
In recent discussions about customer behaviour, a recurring theme has emerged: the belief that providing more information will lead to better decision-making (“If only they knew … then they would …”). While this perspective isn't entirely misplaced, it overlooks a crucial nuance. It's not merely what people know that drives their behaviour, but rather what information is most salient and readily springs to mind in the moment of decision. The Limitation of Knowledge Alone It's easy to assume that if customers simply knew more, they would make better decisions. For instance, knowing how to budget effectively or save money can indeed be useful. Knowing that I should save more for retirement or for investments. That I should eat less red meat for health or sustainability reasons. That I should be careful about what information I share online. These are all real-life examples of issues I’ve worked on where educating customers (or users) might have been a solution – and where helping people ‘know’ why they should do it failed to shift the needle. The critical factor isn't just having the information, but rather how accessible and prominent that information is when it’s needed. The question then is not do I know something, but rather does it spring to mind when it can actually shape my decisions? The Salience of Information in Decision-Making Consider a scenario where a customer interacts with a product or service. The decision-making process is often instantaneous and intuitive, driven by what immediately comes to mind rather than a comprehensive evaluation of all known benefits. This means that the information most salient at the moment—whether it's the immediate cost or a specific feature—has a more significant impact than the general knowledge a customer might have. As an example, I was involved in a project where my client was responding to new environmental regulations – and wanted to find out how to do this without upsetting their customers. The initial solution didn’t work because what was salient – and thus impacted customers responses – was the benefit to the brand not the benefit to the environment. While both benefits were ‘known’ by customers, it wasn’t till small tweaks were made to subtly emphasise and customer support for such actions, that complaints dropped off. A Case in Point: Council Rates Another example where this idea is relevant are the rates (tax) bills that New Zealanders receive from their local council. While residents might be well aware of the benefits their rates support—such as parks, libraries, and community services—this knowledge doesn’t always translate into a positive reaction when the bill arrives. For many, the first thing that springs to mind is the expense, not the benefits. In my case, receiving a $1,000 council rates bill (these are billed quarterly) was a stark reminder of this phenomenon. Despite understanding the value provided by these rates, the immediate focus was on the financial burden. If the benefits were more salient at the time of billing, the experience could be more positive. For instance, if the rates bill included a summary of the value received from various services—like a breakdown showing the value I obtain from the library based on the number of books borrowed—this could shift the focus from the cost to the benefits. In my case, borrowing 35 books over three months at an estimated value of $30 each amount to $1,050 worth of benefits, which highlights the value received far beyond the cost. And of course there are other services that I use as well – my local park that I go running in, the playgrounds that I take my kids to, the roads I drive along or the public transport that is subsidised. I ‘know’ these things, but do they immediately spring to mind when I see my rates bill? Seizing the Opportunity This concept of salience extends beyond council rates. In various customer interactions—such as bills, invoices, loyalty schemes, and product renewals—the opportunity lies in enhancing the salience of positive attributes at the critical moment of engagement. To effectively leverage this understanding, organisations should focus on making the benefits of their products or services more prominent when customers are most engaged and in a way that is relevant to the context. This means designing communications and touchpoints that highlight the value received, not just the cost or features.  While knowledge is important, it's the salience of that knowledge at the moment of decision that truly influences behaviour. By ensuring that the most relevant and positive information is top-of-mind, organisations can improve customer satisfaction and decision-making outcomes.
By Cole Armstrong July 24, 2024
Navigating the Shifting Landscape of Design
By Cole Armstrong March 15, 2024
How do we create persuasive touchpoints that make a difference? By considering how simple ways of reframing our messages, using insights from psychology and behavioural science, can create greater motivation to act.
Show More
Share by: