Blog: Why 100% Test Coverage is Not Enough
|
|
This month, we have a blog post from one of our Software Consultants, Logan Farmer. Logan discusses scenarios in which having 100% test coverage of your application does not guarantee that it is fully tested. I've you'd like to hear more about these scenarios, and recommendations for avoiding gaps in testing, this technical blog post is for you!
Read Logan's blog post here!
|
|
Shingo Systems Design Workshop - April 1-2, 2026
We are excited to announce that Menlo will once again be the host site for a Shingo Workshop, this time in-person at our office in Ann Arbor, MI! This two-day Shingo Systems Design Workshop builds on the foundation established in the DISCOVER EXCELLENCE™ workshop and deepens your understanding of how systems enable organizational excellence.
Through a blend of classroom learning and on-site experiences at Menlo, participants explore the Systems and Tools diamonds of the Shingo Model™, beginning with a core truth: all work in an organization is the outcome of a system. When systems are not intentionally designed to achieve a clear objective, they evolve on their own - driving inconsistent behaviors and variable results.
Learn more or register here! |
|
From the Steam Mop to the Ninja CREAMi
How SharkNinja innovates across industries
|
|
Whether you realize it or not, you’ve probably used a product from SharkNinja sometime in your life. Like Menlo, they work across many industries, building everything from vacuums and hair dryers to the ever-popular Ninja CREAMi. They now operate in 37 distinct product categories! A recent video from The Hustle, titled “Why This Company Is So Good at Making Everything,” explores how SharkNinja has managed to expand so successfully across such diverse markets, with some interesting similarities to our own philosophies.
Their story began with the Shark Steam Mop, launched after their parent company identified a gap in the floor-cleaning market. From there, they continued to expand into new segments like vacuums and blenders. As CEO Mark Barrocas puts it in an interview with The Verge, “We find problems that others don’t see, and we solve problems that others can’t.”
How do they do this? Similar to our High-Tech Anthropologists®, they identify end user's problems by observing them doing everyday tasks. Their new product launches achieve success after success because their products actually solve users everyday problems.
They also differentiate themselves through speed. With global design teams working across time zones, their work never stops. This reminded us of our pairing and rotation model. By regularly rotating pairs on and off projects, we ensure that no work stops simply because one person is out. There’s always shared context, and another Menlonian ready to step in. Over time, this makes a big difference in project quality and timing.
If you enjoy learning about innovative companies, definitely check out the full video below!
|
|
Start Specific, End Big
Designing for disability can unlock better products for everyone
|
|
Expanding on the theme of innovation, we wanted to share the Harvard Business Review article, How Designing with Disability in Mind Sparks Innovation. This article introduces a process called design amplification, the idea that “innovations created for users with accessibility needs can be amplified to unlock universal value”. This means that instead of starting by designing a product for the average population, you start with designing for a specific disability, and look at these constraints as a way to increase innovation. From there, you can identify other types of users who can benefit from the solution, which allows you to eventually expand into mainstream markets.
The authors illustrate this through the example of walk-in tubs. Originally created for seniors with mobility issues, the product evolved to attract athletes, people recovering from injuries, and ultimately mainstream buyers seeking spa-like comfort. What began as an accessibility solution became a $750M+ market!
This is a great approach because it does two important things at once: ensures people with disabilities have products that are intentionally built to serve them, and creates a pathway for those innovations to become commercially successful. This also mirrors how we practice human-centered design. We intentionally design for one clearly defined primary persona, while also considering secondary and tertiary personas. Rather than creating something generic that sort of works for everyone, this approach allows us to build a solution that works exceptionally well for the primary user and still brings meaningful value to others!
Read the full article here!
|
|
The People Economy Podcast
From Dread to Delight: The Joy of Work
Podcast Host: Lathan Craft
Recommended by: Sarah Neam, Marketing Consultant
This month I wanted to recommend an episode of The People Economy Podcast that our very own CEO, Rich Sheridan, was a guest on. This podcast was recently launched by host Lathan Craft, with the focus being around the idea that humans should be at the center of business. Rich had the opportunity to be one of the first guests!
If you enjoy hearing Rich's perspective, are curious to learn more about his back story, or the whys behind Menlo processes, I definitely recommend checking out the episode. Lathan and Rich cover topics like Rich's journey to founding Menlo and how he found joy at work. They also discuss Menlo processes such as pairing, what happened during Covid, and how being a systems thinker is so important in order to actually get things done. And Rich even talks about a potential third book idea he has:)
Check out the episode on YouTube here!
|
|
|
From time to time we run retrospective meetings once a project has been going on for a while. These meetings help us take a step back, reflect on the project, and come up with plans for improvements going forward. We recently held a retro for one of our internal projects, Archie.
Our original goals for Archie were to improve Quality of Life aspects of the application we are building in Harrison (our project with NASA), as well as provide a safe space for learning the Harrison codebase for team members who are new to the project. We used this retro to analyze how well we did achieving these goals. We set up a white board with headers saying “What went well”, “What didn’t go well”, and “Action items/areas for improvement." Everyone had an opportunity to go up to the board and write any thoughts they had under those sections. Afterwards, we went around and discussed each point that was written, frequently either generating more thoughts or action items to work on. In just one hour, we collected 53 points of feedback for improving Archie in the future.
After the retro, the data showed us that not only were we successful in our original goals, but Archie had also become an incredible tool for onboarding. On Archie, Developers have ample opportunities to interact with High-Tech Anthropologists®, Quality Advocates, and Project Managers in a low stakes environment.
While running experiments is always vital, it’s also important to take a step back and reflect on how they go!
Have you recently ran an experiment? Email us!
|
|
|
|