• Tech Book of the Month
  • Archive
  • Recommend a Book
  • Choose The Next Book
  • Sign Up
  • About
  • Search
Tech Book of the Month
  • Tech Book of the Month
  • Archive
  • Recommend a Book
  • Choose The Next Book
  • Sign Up
  • About
  • Search

June 2021 - Letters to the Nomad Partnership 2001-2013 (Nick Sleep's and Qais Zakaria's Investor Letters)

This month we review a unique source of information - mysterious fund manager Nick Sleep’s investment letters. Sleep had an extremely successful run and identified several very interesting companies and characteristics of those companies which made for great investments. He was early to uncover Amazon, Costco, and others - riding their stocks into the stratosphere over the last 20 years. These letters cover the internet bubble, the 08/09 crisis, and all types of interesting businesses across the world.

The full letters can be found here

The full letters can be found here

Tech Themes

  1. Scale Benefits Shared. Nick Sleep’s favored business model is what he calls Scale Benefits Shared. The idea is straight forward and appears across industries. Geico, Amazon, and Costco all have this business model. Its simple - companies start with low prices and spend only on the most important things. Over time as the company scales (more insured drivers, more online orders, more stores) they pass on the benefits of scale to the customer with even further lower prices. The consumer then buys more with the low-cost provider. This has a devastating effect on competition - it forces companies to exit the industry because the one sharing the scale benefits has to become hyper-efficient to continue to make the business model work. “In the case of Costco scale efficiency gains are passed back to the consumer in order to drive further revenue growth. That way customers at one of the first Costco stores (outside Seattle) benefit from the firm’s expansion (into say Ohio) as they also gain from the decline in supplier prices. This keeps the old stores growing too. The point is that having shared the cost savings, the customer reciprocates, with the result that revenues per foot of retailing space at Costco exceed that at the next highest rival (WalMart’s Sam’s Club) by about fifty percent.” Jeff Bezos was also very focused on this, his 2006 annual letter highlighted as much: “Our judgment is that relentlessly returning efficiency improvements and scale economies to customers in the form of lower prices creates a virtuous cycle that leads over the long-term to a much larger dollar amount of free cash flow, and thereby to a much more valuable Amazon.com. We have made similar judgments around Free Super Saver Shipping and Amazon Prime, both of which are expensive in the short term and – we believe – important and valuable in the long term.” So what companies today are returning scale efficiencies with customers? One recent example is Snowflake - which is a super expensive solution but is at least posturing correctly in favor of this model - the recent earnings call highlighted that they had figured out a better way to store data, resulting in a storage price decrease for customers. Fivetran’s recent cloud data warehouse comparison showed Snowflake was both cheaper and faster than competitors Redshift and Bigquery - a good spot to be in! Another example of this might be Cloudflare - they are lower cost than any other CDN in the market and have millions of free customers. Improvements made to the core security+CDN engine, threat graph, and POP locations result in better performance for all of their free users, which leads to more free users, more threats, vulnerabilities, and location/network demands - a very virtuous cycle!

  2. The Miracle of Compound Growth & Its Obviousness. While appreciated in some circles, compounding is revered by Warren Buffett and Nick Sleep - it’s a miracle worth celebrating every day. Sleep takes this idea one step further, after discussing how the average hold period of stocks has fallen significantly over the past few decades: “The fund management industry has it that owning shares for a long time is futile as the future is unknowable and what is known is discounted. We respectfully disagree. Indeed, the evidence may suggest that investors rarely appropriately value truly great companies.” This is quite a natural phenomenon as well - when Google IPO’d in 2004 for a whopping $23bn, were investors really valuing the company appropriately? Were Visa ($18Bn valuation, largest US IPO in history) and Mastercard ($5.3Bn valuation) being valued appropriately? Even big companies like Apple in 2016 valued at $600Bn were arguably not valued appropriately. Hindsight is obvious, but the durability of compounding in great businesses is truly a myth to behold. That’s why Sleep and Zakaria wound down the partnership in 2014, opting to return LP money and only own Berkshire, Costco, and Amazon for the next decade (so far that’s been a great decision!). While frequently cited as a key investing principle, compounding in technology, experiences, art, and life are rarely discussed, maybe because they are too obvious. Examples of compounding (re-investing interest/dividends and waiting) abound: Moore’s Law, Picasso’s art training, Satya Nadella’s experience running Bing and Azure before becoming CEO, and Beatles playing clubs for years before breaking on the scene. Compounding is a universal law that applies to so much!

  3. Information Overload. Sleep makes a very important but subtle point toward the end of his letters about the importance of reflective thinking:

    BBC Interviewer: “David Attenborough, you visited the North and South Poles, you witnessed all of life in-between from the canopies of the tropical rainforest to giant earthworms in Australia, it must be true, must it not, and it is a quite staggering thought, that you have seen more of the world than anybody else who has ever lived?”

    David Attenborough: “Well…I suppose so…but then on the other hand it is fairly salutary to remember that perhaps the greatest naturalist that ever lived and had more effect on our thinking than anybody, Charles Darwin, only spent four years travelling and the rest of the time thinking.”

    Sleep: “Oh! David Attenborough’s modesty is delightful but notice also, if you will, the model of behaviour he observed in Charles Darwin: study intensely, go away, and really think.”

    There is no doubt that the information age has ushered in a new normal for daily data flow and news. New information is constant and people have the ability to be up to date on everything, all the time. While there are benefits to an always-on world, the pace of information flow can be overwhelming and cause companies and individuals to lose sight of important strategic decisions. Bill Gates famously took a “think week” each year where he would lock himself in a cabin with no internet connection and scan over hundreds of investment proposals from Microsoft employees. A Harvard study showed that reflection can even improve job performance. Sometimes the constant data flow can be a distraction from what might be a very obvious decision given a set of circumstances. Remember to take some time to think!

principal-agent-problem.png
image-13.png

Business Themes

  1. Psychological Mistakes. Sleep touches on several different psychological problems and challenges within investing and business, including the role of Social Proof in decision making. Social proof occurs when individuals look to others to determine how to behave in a given situation. A classic example of Social Proof comes from an experiment done by Psychologist, Stanley Milgram, in which he had groups of people stare up at the sky on a crowded street corner in New York City. When five people were standing and looking up (as opposed to a single person), many more people also stopped to look up, driven by the group behavior. This principle shows up all the time in business and is a major proponent in financial bubbles. People see others making successful investments at high valuations and that drives them to do the same. It can also drive product and strategic decisions - companies launching dot-com names in the 90’s to drive their stock price up, companies launching corporate venture arms in rising markets, companies today deciding they need a down-market “product-led growth” engine. As famed investor Stan Druckenmiller notes, its hard to sit idly by while others (who may be less informed) crush certain types of investments: “I bought $6 billion worth of tech stocks, and in six weeks I had lost $3 billion in that one play. You asked me what I learned. I didn’t learn anything. I already knew that I wasn’t supposed to do that. I was just an emotional basketcase and I couldn’t help myself. So maybe I learned not to do it again, but I already knew that.”

  2. Incentives, Psychology, and Ownership Mindset. Incentives are incredibly powerful in business and its surprisingly difficult to get people to do the right thing. Sleep spends a lot of time on incentives and the so-called Principal-Agent Conflict. Often times the Principal (Owner, Boss, Purchaser, etc.) may employ an Agent (Employee, Contractor, Service) to accomplish something. However the goals and priorities of the principal may not align with that agent. As an example, when your car breaks down and you need to go to a local mechanic to fix it, you (the principal) want to find someone to fix the car as well and as cheaply as possible. However, the agent (the mechanic) may be incentivized to create the biggest bill possible to drive business for their garage. Here we see the potential for misaligned incentives. After 5 years of really strong investment results, Sleep and Zakaria noticed a misaligned incentive of their own: “Which brings me to the subject of the existing performance fee. Eagle-eyed investors will not have failed but notice the near 200 basis point difference between gross and net performance this year, reflecting the performance fee earned. We are in this position because performance for all investors is in excess of 6% per annum compounded. But given historic performance, that may be the case for a very long time. Indeed, we are so far ahead of the hurdle that if the Partnership now earned pass-book rates of return, say 5% per annum, we would continue to “earn” 20% performance fees (1% of assets) for thirty years, that is, until the hurdle caught up with actual results. During those thirty years, which would see me through to retirement, we would have added no value over the money market rates you can earn yourself, but we would still have been paid a “performance fee”. We are only in this position because we have done so well, and one could argue that contractually we have earned the right by dint of performance, but just look at the conflicts!” They could have invested in treasury bonds and collected a performance fee for years to come but they knew that was unfair to limited partners. So the duo created a resetting fee structure, that allowed LPs to claw back performance fees if Nomad did not exceed the 6% hurdle rate for a given year. This kept the pair focused on driving continued strong results through the life of the partnership.

  3. Discovery & Pace. Nick Sleep and Qais Zakaria looked for interesting companies in interesting situations. Their pace is simply astounding: “When Zak and I trawled through the detritus of the stock market these last eighteen months (around a thousand annual reports read and three hundred companies interviewed)…” Sleep and Zakaria put up numbers: 55 annual reports per month (~2 per day), 17 companies interviewed per month (meeting every other day)! That is so much reading. Its partially unsurprising that after a while they started to be able to find things in the annual reports that piqued their interest. Not only did they find retrospectively obvious gems like Amazon and Costco, they also looked all around the world for mispricings and interesting opportunities. One of their successful international investments took place in Zimbabwe, where they noticed significant mispricing involving the Harare Stock Exchange, which opened in 1896 but only started allowing foreign investment in 1993. While Nomad certainly made its name on the Scaled efficiencies shared investment model, Zimbabwe offered Sleep and Zakaria to prioritize their second model: “We have little more than a handful of distinct investment models, which overlap to some extent, and Zimcem is a good example of a second model namely, ‘deep discount to replacement cost with latent pricing power.’” Zimcem was the country’s second-largest cement producer, which traded at a massive discount to replacement cost due to terrible business conditions (inflation growing faster than the price of cement). Not only did Sleep find a weird, mispriced asset, he also employed a unique way of acquiring shares to further increase his margin of safety. “The official exchange rate at the time of writing is Z$9,100 to the U$1. The unofficial, street rate is around Z$17,000 to the U$1. In other words, the Central Bank values its own currency at over twice the price set by the public with the effect that money entering the country via the Central Bank buys approximately half as much as at the street rate. Fortunately, there is an alternative to the Central Bank for foreign investors, which is to purchase Old Mutual shares in Johannesburg, re-register the same shares in Harare and then sell the shares in Harare. This we have done.“ By doing this, Nomad was able to purchase shares at a discounted exchange rate (they would also face the exchange rate on sale, so not entirely increasing the margin of safety). The weird and off the beaten path investments and companies can offer rich rewards to those who are patient. This was the approach Warren Buffett employed early on in his career, until he started focusing on “wonderful businesses” at Charlie Munger’s recommendation.

Dig Deeper

  • Overview of Several Scale Economies Shared Businesses

  • Investor Masterclass Learnings from Nick Sleep

  • Warren Buffett & Berkshire’s Compounding

  • Jim Sinegal (Costco Founder / CEO) - Provost Lecture Series Spring 2017

  • Robert Cialdini - Mastering the Seven Principles of Influence and Persuasion

tags: Costco, Warren Buffett, Berkshire Hathaway, Geico, Jim Sinegal, Cloudflare, Snowflake, Visa, Mastercard, Google, Fivetran, Walmart, Apple, Azure, Bing, Satya Nadella, Beatles, Picasso, Moore's Law, David Attenborough, Nick Sleep, Qais Zakaria, Charles Darwin, Bill Gates, Microsoft, Stanley Druckenmiller, Charlie Munger, Zimbabwe, Harare
categories: Non-Fiction
 

July 2020 - Innovator's Dilemma by Clayton Christensen

This month we review the technology classic, the Innovator’s Dilemma, by Clayton Christensen. The book attempts to answer the age-old question: why do dominant companies eventually fail?

Tech Themes

  1. The Actual Definition of Disruptive Technology. Disruption is a term that is frequently thrown around in Silicon Valley circles. Every startup thinks its technology is disruptive, meaning it changes how the customer currently performs a task or service. The actual definition, discussed in detail throughout the book, is relatively specific. Christensen re-emphasizes this distinction in a 2015 Harvard Business Review article: "Specifically, as incumbents focus on improving their products and services for their most demanding (and usually most profitable) customers, they exceed the needs of some segments and ignore the needs of others. Entrants that prove disruptive begin by successfully targeting those overlooked segments, gaining a foothold by delivering more-suitable functionality—frequently at a lower price. Incumbents, chasing higher profitability in more-demanding segments, tend not to respond vigorously. Entrants then move upmarket, delivering the performance that incumbents' mainstream customers require, while preserving the advantages that drove their early success. When mainstream customers start adopting the entrants' offerings in volume, disruption has occurred." The book posits that there are generally two types of innovation: sustaining and disruptive. While disruptive innovation focuses on low-end or new, small market entry, sustaining innovation merely continues markets along their already determined axes. For example, in the book, Christensen discusses the disk drive industry, mapping out the jumps which pack more memory and power into each subsequent product release. There is a slew of sustaining jumps for each disruptive jump that improves product performance for existing customers but doesn't necessarily get non-customers to become customers. It is only when new use cases emerge, like rugged disk usage and PCs arrive, that disruption occurs. Understanding the specific definition can help companies and individuals better navigate muddled tech messaging; Uber, for example, is shown to be a sustaining technology because its market already existed, and the company didn't offer lower prices or a new business model. Understanding the intricacies of the definition can help incumbents spot disruptive competitors.

  2. Value Networks. Value networks are an underappreciated and somewhat confusing topic covered in The Innovator's Dilemma's early chapters. A value network is defined as "The context within which a firm identifies and responds to customers' needs, solves problems, procures input, reacts to competitors, and strives for profit." A value network seems all-encompassing on the surface. In reality, a value network serves to simplify the lens through which an organization must make complex decisions every day. Shown as a nested product architecture, a value network attempts to show where a company interacts with other products. By distilling the product down to its most atomic components (literally computer hardware), we can see all of the considerations that impact a business. Once we have this holistic view, we can consider the decisions and tradeoffs that face an organization every day. The takeaway here is that organizations care about different levels of performance for different products. For example, when looking at cloud computing services at AWS, Azure, or GCP, we see Amazon EC2 instances, Azure VMs, and Google Cloud VMs with different operating systems, different purposes (general, compute, memory), and different sizes. General-purpose might be fine for basic enterprise applications, while gaming applications might need compute-optimized, and real-time big data analytics may need a memory-optimized VM. While it gets somewhat forgotten throughout the book, this point means that organizations focused on producing only compute-intensive machines may not be the best for memory-intensive, because the customers of the organization may not have a use for them. In the book's example, some customers (of bigger memory providers) looked at smaller memory applications and said there was no need. In reality, there was massive demand in the rugged, portable market for smaller memory disks. When approaching disruptive innovation, it's essential to recognize your organization's current value network so that you don't target new technologies at those who don't need it.

  3. Product Commoditization. Christensen spends a lot of time describing the dynamics of the disk drive industry, where companies continually supplied increasingly smaller drives with better performance. Christensen's description of commoditization is very interesting: "A product becomes a commodity within a specific market segment when the repeated changes in the basis of competition, completely play themselves out, that is, when market needs on each attribute or dimension of performance have been fully satisfied by more than one available product." At this point, products begin competing primarily on price. In the disk drive industry, companies first competed on capacity, then on size, then on reliability, and finally on price. This price war is reminiscent of the current state of the Continuous Integration / Continuous Deployment (CI/CD) market, a subsegment of DevOps software. Companies in the space, including Github, CircleCI, Gitlab, and others are now competing primarily on price to win new business. Each of the cloud providers has similar technologies native to their public cloud offerings (AWS CodePipeline and CloudFormation, GitHub Actions, Google Cloud Build). They are giving it away for free because of their scale. The building block of CI/CD software is git, an open-source version control system founded by Linux founder Linus Torvalds. With all the providers leveraging a massive open-source project, there is little room for true differentiation. Christensen even says: "It may, in fact, be the case that the product offerings of competitors in a market continue to be differentiated from each other. But differentiation loses its meaning when the features and functionality have exceeded what the market demands." Only time will tell whether these companies can pivot into burgeoning highly differentiated technologies.

Business Themes

Innovator Dilemma.png
R1512B_BIG_MODEL-1200x1035.png
  1. Resources-Processes-Value (RPV) Framework. The RPV framework is a powerful lens for understanding the challenges that large businesses face. Companies have resources (people, assets, technology, product designs, brands, information, cash, relationships with customers, etc.) that can be transformed into greater value products and services. The way organizations go about converting these resources is the organization's processes. These processes can be formal (documented sales strategies, for example) or informal (culture and habitual routines). Processes are the big reasons organizations struggle to deal with emerging technologies. Because culture and habit are ingrained in the organization, the same process used to launch a mature, slow-growing market may be applied to a fast-growing, dynamic sector. Christensen puts it best: "This means the very mechanisms through which organizations create value are intrinsically inimical to change." Lastly, companies have values, or "the standards by which employees make prioritization decisions." When there is a mismatch between the resources, processes, and values of an organization and the product or market that an organization is chasing, its rare the business can be successful in competing in the disruptive market. To see this misalignment in action, Christensen describes a meeting with a CEO who had identified the disruptive change happening in the disk-drive market and had gotten a product to market to meet the growing market. In response to a publication showing the fast growth of the market, the CEO lamented to Christensen: "I know that's what they think, but they're wrong. There isn't a market. We've had that drive in our catalog for 18 months. Everyone knows we've got it, but nobody wants it." The issue was not the product or market demand, but the organization's values. As Christensen continues, "But among the employees, there was nothing about an $80 million, low-end market that solved the growth and profit problems of a multi-billion dollar company – especially when capable competitors were doing all they could to steal away the customers providing those billions. And way at the other end of the company there was nothing about supplying prototype companies of 1.8-inch drives to an automaker that solved the problem of meeting the 1994 quotas of salespeople whose contacts and expertise were based so solidly in the computer industry." The CEO cared about the product, but his team did not. The RPV framework helps evaluate large companies and the challenges they face in launching new products.

  2. How to manage through technological change. Christensen points out three primary ways of managing through disruptive technology change: 1. "Acquire a different organization whose processes and values are a close match with the new task." 2. "Try to change the processes and values of the current organization." 3. "Separate out an independent organization and develop within it the new processes and values that are required to solve the new problem." Acquisitions are a way to get out ahead of disruptive change. There are so many examples but two recent ones come to mind: Microsoft's acquisition of Github and Facebook's acquisition of Instagram. Microsoft paid a whopping $7.5B for Github in 2018 when the Github was rumored to be at roughly $200M in revenue (37.5x Revenue multiple!). Github was undoubtedly a mature business with a great product, but it didn't have a ton of enterprise adoption. Diane Greene at Google Cloud, tried to get Sundar Pichai to pay more, but he said no. Github has changed Azure's position within the market and continued its anti-Amazon strategy of pushing open-source technology. In contrast to the Github acquisition, Instagram was only 13 employees when it was acquired for $1B. Zuckerberg saw the threat the social network represented to Facebook, and today the acquisition is regularly touted as one of the best ever. Instagram was developing a social network solely based on photographs, right at the time every person suddenly had an excellent smartphone camera in their pocket. The acquisition occurred right when the market was ballooning, and Facebook capitalized on that growth. The second way of managing technological change is through changing cultural norms. This is rarely successful, because you are fighting against all of the processes and values deeply embedded in the organization. Indra Nooyi cited a desire to move faster on culture as one of her biggest regrets as a young executive: "I’d say I was a little too respectful of the heritage and culture [of PepsiCo]. You’ve got to make a break with the past. I was more patient than I should’ve been. When you know you have to make a change, at some point you have to say enough is enough. The people who have been in the company for 20-30 years pull you down. If I had to do it all over again, I might have hastened the pace of change even more." Lastly, Christensen prescribes creating an independent organization matched to the resources, processes, and values that the new market requires. Three great spin-out, spin-in examples with different flavors of this come to mind. First, Cisco developed a spin-ins practice whereby they would take members of their organization and start a new company that they would fund to develop a new process. The spin-ins worked for a time but caused major cultural issues. Second, as we've discussed, one of the key reasons AWS was born was that Chris Pinkham was in South Africa, thousands of miles away from Amazon Corporate in Seattle; this distance and that team's focus allowed it to come up with a major advance in computing. Lastly, Mastercard started Mastercard Labs a few years ago. CEO Ajay Banga told his team: "I need two commercial products in three years." He doesn't tell his CFO their budget, and he is the only person from his executive team that interacts with the business. This separation of resources, processes, and values allows those smaller organizations to be more nimble in finding emerging technology products and markets.

  3. Discovering Emerging Markets.

    The resources-processes-values framework can also show us why established firms fail to address emerging markets. Established companies rely on formal budgeting and forecasting processes whereby resources are allocated based on market estimates and revenue forecasts. Christensen highlights several important factors for tackling emerging markets, including focusing on ideas, failure, and learning. Underpinning all of these ideas is the impossibility of predicting the scale and growth rate of disruptive technologies: "Experts' forecasts will always be wrong. It is simply impossible to predict with any useful degree of precision how disruptive products will be used or how large their markets will be." Because of this challenge, relying too heavily on these estimates to underpin financial projections can cause businesses to view initial market development as a failure or not worthy of the companies time. When HP launched a new 1.3-inch disk drive, which could be embedded in PDAs, the company mandated that its revenues had to scale up to $150M within three years, in line with market estimates. That market never materialized, and the initiative was abandoned as a failed investment. Christensen argues that because disruptive technologies are threats, planning has to come after action, and thus strategic and financial planning must be discovery-based rather than execution-based. Companies should focus on learning their customer's needs and the right business model to attack the problem, rather than plan to execute their initial vision. As he puts it: "Research has shown, in fact, that the vast majority of successful new business ventures, abandoned their original business strategies when they began implementing their initial plans and learned what would and would not work." One big fan of Christensen's work is Jeff Bezos, and its easy to see why with Amazon's focus on releasing new products in this discovery manner. The pace of product releases is simply staggering (~almost one per day). Bezos even talked about this exact issue in his 2016 shareholder letter: "The senior team at Amazon is determined to keep our decision-making velocity high. Speed matters in business – plus a high-velocity decision making environment is more fun too. We don't know all the answers, but here are some thoughts. First, never use a one-size-fits-all decision-making process. Many decisions are reversible, two-way doors. Those decisions can use a light-weight process. For those, so what if you're wrong? I wrote about this in more detail in last year's letter. Second, most decisions should probably be made with somewhere around 70% of the information you wish you had. If you wait for 90%, in most cases, you're probably being slow." Amazon is one of the first large organizations to truly embrace this decision-making style, and clearly, the results speak for themselves.

Dig Deeper

  • What Jeff Bezos Tells His Executives To Read

  • Github Cuts Subscription Price by More Than Half

  • Ajay Banga Opening Address at MasterCard Innovation Forum 2014

  • Clayton Christensen Describing Disruptive Innovation

  • Why Cisco’s Spin-Ins Never Caught On

tags: Amazon, Google Cloud, Microsoft, Azure, Github, Gitlab, CircleCI, Pepsi, Jeff Bezos, Indra Nooyi, Mastercard, Ajay Banga, HP, Uber, RPV, Facebook, Instagram, Cisco, batch2
categories: Non-Fiction
 

October 2019 - The Design of Everyday Things by Don Norman

Psychologist Don Norman takes us through an exploratory journey of the basics in functional design. As the consumerization of software grows, this book’s key principles will become increasingly important.

Tech Themes

  1. Discoverability and Understanding. Discoverability and Understanding are two of the most key principles in design. Discoverability answers the questions of, “Is it possible to figure out what actions are possible and where and how to perform them?” Discoverability is absolutely crucial for first time application users because poor discovery of actions leads to low likelihood of repeat use. In terms of Discoverability, Scott Berkun notes that designers should prioritize what can be discovered easily: “Things that most people do, most often, should be prioritized first. Things that some people do, somewhat often, should come second. Things that few people do, infrequently, should come last.” Understanding answers the questions of: “What does it all mean? How is the product supposed to be used? What do all the different controls and settings mean?” We have all seen and used applications where features and complications dominate the settings and layout of the app. Understanding is simply about allowing the user to make sense of what is going on in the application. Together, Discoverability and Understanding lay the ground work for successful task completion before a user is familiar with an application.

  2. Affordances, Signifiers and Mappings. Affordances represent the set of possible actions that are possible; signifiers communicate the correct action that should take place. If we think about a door, depending on the design, possible affordances could be: push, slide, pull, twist the knob, etc. Signifiers represent the correct action or the action the designer would like you to perform. In the context of a door, a signifier might be a metal plate that makes it obvious that the door must be pushed. Mappings provide straightforward correspondence between two sets of objects. For example, when setting the brightness on an iPhone, swiping up increases brightness and swiping down decreases brightness, as would be expected by a new user. Design issues occur when there is a mismatch in affordances, signifiers and mappings. Doors provide another great example of poor coordination between affordances, signifiers and mappings - everyone has encountered a door with a handle that says push over it. This normally followed by an uncomfortable pushing and pulling motion to discover the actions possible with the door. Why are there handles if I am supposed to push? Good design and alignment between affordances, signifiers and mappings make life easier for everyone.

  3. The Seven Stages of Action. Norman lay outs the psychology underpinning user decisions in seven stages - Goal, Plan, Specify, Perform, Perceive, Interpret, Compare. The first three (Goal, Plan, Specify) represent the clarification of an action to be taken on the World. Once the action is Performed, the final three steps (Perceive, Interpret, Compare) are trying to make sense of the new state of the World. The seven stages of action help generalize the typical user’s interactions with the World. With these stages in mind, designers can understand potential breakdowns in discoverability, understanding, affordances, signifiers, and mappings. As users perform actions within applications, understanding each part of the customer journey allows designers to prioritize feature development and discoverability.

Business Themes

Normans-seven-stages-of-action-Redrawn-from-Norman-2001.png
  1. The best product does not always win, but... If the best product always won out, large entrenched incumbents across the software ecosystem like IBM, Microsoft, Google, SAP, and Oracle would be much smaller companies. Why are there so many large behemoths that won’t fall? Each company has made deliberate design decisions to reduce the amount of customer churn. While most of the large enterprise software providers suffer from Feature Creep, the product and deployment complexity can often be a deterrent to churn. For example, Enterprise CIOs do not want to spend budget to re-platform from AWS to Azure, unless there was a major incident or continued frustration with ease of use. Interestingly enough though, as we’ve discussed, the transition from license-maintenance software to SaaS, as well as the consumerization of the enterprise, are changing the necessity of good design and user experience. If we look at Oracle for example. The business has made several acquisitions of applications to be built on Oracle Databases. But the poor user experience and complexity of the applications is starting to push Oracle out of businesses.

  2. Shipping products on time and on budget. “The day a product development process starts, it is behind schedule and above budget.” The product design process is often long and complex because there is a wide array of disciplines involved in the process. Each discipline thinks they are the most important part of the process and may have different reasons for including a singular feature, which may conflict with good design. To alleviate some of that complexity, Norman suggests hiring design researchers that are separate from the product development focus. These researchers focus on how users are working in the field and are coming up with additional use cases / designs all the time. When the development process kicks off, target features and functionality have already been suggested.

  3. Why should business leaders care about good design? We have already discussed how product design can act as a deterrent to churn. If processes and applications become integral to Company function, then there is a low chance of churn, unless there is continued frustration with ease of use. Measuring product market fit is difficult but from a metrics perspective; companies can look at gross churn ($ or customer amount that left / beginning ARR or beginning customers) or NPS to judge how well their product is being received. Good design is a direct contributor to improved NPS and better retention. When you complement good design with several hooks into the customers, churn reduces.

Dig Deeper

  • UX Fundamentals from General Assembly

  • Why game design is crucial for preventing churn

  • Figma and InVision - the latest product development tools

  • Examples of bad user experience design

  • Introduction to Software Usage Analytics

tags: Internet, UX, UI, Design, Apple, App Store, AWS, Azure, Amazon, Microsoft, Oracle, batch2
categories: Non-Fiction
 

About Contact Us | Recommend a Book Disclaimer