Chapter 1
Joy in the Machine: How One Company Reimagined Work
In 2012, Inc. magazine's Leigh Buchanan declared Menlo Innovations "The Most Joyful Company in America." This wasn't hyperbole-it was recognition of something revolutionary happening in a basement office in Ann Arbor, Michigan. Founded by Rich Sheridan in 2001 amid the dot-com crash, Menlo has since won multiple Inc. magazine growth awards, tripled its office space three times, and become a global destination for those seeking workplace transformation. Each year, thousands of visitors from companies like USAA, Steelcase, Disney, and Nike make pilgrimages to witness Menlo's radically different approach to work. What are they seeking? Joy-a way out of fear, meaningless work, and toxic corporate culture. The book has become a manifesto for workplace revolutionaries, with readers like Christian writing to Sheridan saying simply: "You saved me." In a world where 70% of workers report being disengaged, Menlo offers something precious: proof that there's a better way.
Chapter 2
The Journey from Passion to Disillusionment and Back
At thirteen, Rich Sheridan fell in love with programming when he typed a simple two-line program that made a computer respond "HI RICH." This magical moment sparked a lifelong passion. By high school, he was creating fantasy baseball games and leading programming teams. The early days were intoxicating-filled with energy, camaraderie, and the thrill of creation.
Yet despite external success-degrees from the University of Michigan, promotions from programmer to vice president, stock options worth millions-by mid-career, Sheridan wanted out. Behind the facade of success lay exhaustion: long nights away from family, impossible-to-schedule vacations, troubled projects, disappointed colleagues, and constant customer complaints. By 1997, at forty, when offered another VP position, he initially rejected it despite the financial rewards. His passion was dying; he'd spend mornings taking long drives to arrive at work as late as possible, then waste half his day playing FreeCell with his screen turned away from the door.
The turning point came in 1999 when Sheridan discovered two game-changers within weeks: Kent Beck's writings on "Extreme Programming" and a Nightline episode about design firm IDEO. Both revealed radically different approaches to work-open workspaces, collaborative programming, direct customer involvement, and conscious design thinking. With the support of his executive team and James Goebel as his transformation partner, Sheridan set out to revolutionize how his team worked.
The initial resistance was fierce. When he presented Extreme Programming to his fourteen software engineers, one responded: "Blood, mayhem, murder. Don't do it, Rich. Don't make us share computers or code." Yet two seasoned developers volunteered to try the approach. Three weeks in, one stopped Sheridan in the parking lot asking if he'd still be paid since he was having so much fun it didn't feel like work anymore-the same developer who'd recently asked for a reference to leave the company.
Sheridan's team transformed an abandoned factory floor into a collaborative workspace with simple folding tables and chairs. A week-long Java training experiment using Extreme Programming techniques produced immediate results: energy, noise, collaboration, progress, learning, and fun. Despite initial resistance to making this permanent, Sheridan stood firm: "This is the way we are going to work from now on."
The transformation helped make Interface Systems the top-performing public company in Michigan, with stock soaring from $2 to $80 per share. When asked why he risked such dramatic change despite his comfortable position, Sheridan explained that staying the same posed the greater risk-the part of him that loved his work was dying. Eventually, Interface was acquired, but when the Internet bubble burst in 2001, Sheridan found himself unemployed for the first time in his career.
From those ashes, four former colleagues founded Menlo Innovations in June 2001, despite the industry's collapse around them. Their purpose: bring joy to the world through software and teach others their practices. Today, Sheridan's passion burns brighter than ever, and his children are convinced he'll never retire.
Chapter 3
The Physical Environment of Joy
Walk into Menlo's 17,000-square-foot basement space, and the difference is immediately apparent. Unlike sterile, silent cubicle farms, this "factory" pulses with energy, chatter, and activity. There are no walls, offices, cubes, or doors (except for security and bathrooms). Lightweight aluminum tables with one computer each are pushed close together with pairs of people sitting even closer. Power comes from retractable cables hanging from high ceilings. The concrete floors accommodate both dogs and babies.
"I don't know what you do," a delivery person once remarked, "but whatever it is, I want to work here."
Inspired by the M*A*S*H television show, Menlo embraces mobility and flexibility. Like the 4077th unit that could relocate quickly when needed, they've designed their workspace with lightweight, movable equipment. Three times in their history, they've "bugged out" to larger spaces, breaking down their entire operation on Saturday and reassembling in the new location on Sunday, never missing a workday due to a move.
The team rearranges their factory constantly-weekly or even daily. With well-placed wiring and lightweight tables, anyone can reconfigure the space without permission. No facilities staff required. Teams typically rearrange for two reasons: either to accommodate new projects by grouping related team members together, or simply to shake things up when they've been in the same spot too long. On Fridays, teams might grab beer and spend a few hours rearranging just to change their perspective.
At Menlo, there is no corner office for executives. As CEO, Sheridan sits at a five-foot aluminum table identical to everyone else's, with an old white Apple iMac that's probably the slowest computer in the company. His table sits right in the middle of the action, and sometimes the team moves him closer to challenging projects so he can overhear more details.
Most conversations happen in the open because Sheridan wants his team to hear client interactions-they care about customers as much as he does and might have valuable insights to contribute. What some might call eavesdropping, he considers healthy curiosity from a team focused on shared goals.
The Menlo Software Factory hums with conversation and laughter-you can hear work happening. While many believe "flow" requires library quiet (evidenced by widespread headphone use), Menlo's flow is different-it's team flow, not personal flow. They ban earbuds because they work noisily together. Critics claim concentration is impossible in such an environment, forgetting about annoying colleagues in traditional offices who disrupt with personal calls or social visits. At Menlo, conversations focus on problem-solving and design challenges, creating a respectful current of useful noise.
This changeable, open space encourages serendipity. The greatest value comes from people overhearing others' ideas, creating opportunities for innovation. In closed environments where tired, stressed workers block out the world with earbuds or closed doors, these innovative sparks never happen.
Chapter 4
The Power of Pairing: Two Heads Are Better Than One
At Menlo, every task is performed by pairs of people working together at a single computer. This isn't just an occasional collaboration-it's their fundamental approach to work. Each week, pairs rotate to new partners and projects, creating a constant flow of knowledge throughout the organization.
This pairing system reveals hidden talents through casual conversation-like discovering a programmer's voice recognition experience that proves valuable for a client. Learning happens continuously as pairs work together, with one person teaching their new partner what they learned the previous week. For example, High-Tech Anthropologist Michelle learns about prosthetics one week, then teaches Laura everything relevant to their software design the next week. This teaching reinforces Michelle's own understanding.
Weekly pair rotation prevents alienation and cliques while fostering deeper connections. After spending forty hours in conversation with a teammate, people develop relationships beyond surface impressions. Pairing also provides an emotional safety net when facing new challenges-like two frightened children who find courage together when holding hands.
Despite appearing inefficient, pairing actually increases productivity as stuck people get quickly unstuck, quality improves with four eyes on the screen, and distractions disappear. New hires are often exhausted after their first days because they're actually working productively for a full eight hours-unlike typical office environments where informal research suggests programmers only work about four effective hours daily due to meetings, interruptions, and digital distractions.
Pairing also eliminates dangerous "towers of knowledge"-those individuals whose technical expertise no one else possesses. When Rich became VP of R&D at Interface Systems, a board member immediately asked about "Dave"-the key tower of knowledge the company depended on. But these towers of knowledge aren't happy either-what starts as job security becomes a prison. They become the organization's bottleneck, unable to take vacations without bringing their laptop, and watching new colleagues get exciting projects while they're trapped in their specialty.
At Menlo, weekly pair rotation eliminates knowledge hoarding completely, allowing them to never deny time-off requests and preventing the dangerous situation where critical knowledge exists in only one person's head. The hidden benefit of learning freedom is that team members embrace teaching. Knowledge isn't hoarded in personal vaults. Workers become more valuable and flexible by mastering multiple technologies and domains.
Beyond pairing, Menlo hosts weekly "Lunch 'n Learn" sessions to accelerate knowledge transfer across the entire team. Topics typically relate to client work-like Android development or brainstorming techniques. While teaching, Menlonians also develop presentation skills and confidence speaking to groups. These sessions have become community affairs, with visitors welcome to attend.
Menlo also offers formal classes about their process and culture to paying clients from organizations worldwide. Team members create and deliver curriculum on "The Menlo Way," High-Tech Anthropology, project management techniques, and software development approaches. Nothing is a trade secret-their mission is to "end human suffering in the world as it relates to technology," which means helping everyone have better work lives.
Chapter 5
Rituals and Artifacts: The Backbone of Culture
Traditional meetings waste time and energy. At Menlo, they've eliminated unproductive gatherings and replaced rules and bureaucracy with predictable rituals, ceremonies, and storytelling events that have clear structure and purpose.
Instead of unproductive weekly status meetings, they hold a daily standup at 10 a.m. sharp that typically finishes in under thirteen minutes. A dartboard alarm signals the start, and everyone gathers in a circle. Someone grabs their iconic seven-dollar Viking helmet (perfect for pairs, with its two horns), and each pair describes their work and where they might need help as the helmet passes around the circle. The last pair closes with "Be careful out there." This democratic, inclusive ritual gives everyone equal voice with no one running the meeting.
They avoid email and electronic communication within the company, instead using what they call "High-Speed Voice Technology"-simply talking to each other. When Rich needs Emily's attention, he calls "Hey, Emily!" across the room. She replies, "Hey, Rich!" and they communicate in seconds without scheduling or interrupting others. For company-wide announcements, he calls "Hey, Menlo!" and everyone responds "Hey, Rich!" as the office falls silent.
To break up the afternoon, they created the "walkies" tradition. At 3 p.m., Jeff J. (their playful "VP of High-Speed Voice Technology") calls out "Walkies!" and the team takes a walk around the building. Interestingly, even during these breaks, pairs often stay together discussing their current work.
One of their most valuable rituals is developing communication skills. Everyone gets opportunities to present in front of groups-during weekly kickoffs, customer Show & Tells, local conferences, and factory tours. These rituals also encourage healthy debate. When creating something innovative, spirited team debate produces better outcomes.
At Menlo, all estimates come from the team doing the actual work. Their weekly estimation ritual involves project teams discussing story cards together, with each pair independently estimating how long tasks will take. Estimates can only be 2, 4, 8, 16, 32, or 64 hours. They don't force consensus-different pairs may estimate differently based on experience and skills.
Their weekly Show & Tell ritual resolves the disconnect between what sponsors envision and what teams build. The client explains the work back to them, demonstrating their understanding while the team listens. This reversal ensures clients are actively engaged while clarifying whether both sides share the same vision.
Most projects drift into ambiguity after launch as sponsors lose track of progress. Menlo's weekly planning game prevents this using "Planning Origami"-folded paper story cards representing features and time estimates placed on planning sheets representing available weekly hours. This simple exercise facilitates crucial priority discussions among competing stakeholders. By the end, priorities are crystal clear: cards on planning sheets will be worked on; those not on sheets won't be.
After planning, project managers assign story cards to pairs using their celebrated Work Authorization Board-a visual matrix where columns represent pairs and rows represent days of the week. This "tyrannical" system creates freedom: each pair knows exactly what to work on without managers constantly checking in. Pairs work sequentially from top to bottom on one card at a time until stuck or finished, then move to the next card.
Their work authorization board uses sticky dots to provide instant project status visibility without meetings or conversations. Yellow dots indicate work in progress, orange means "we think we're done," and green confirms completion after QA review. Red dots signal failed QA with explanations on attached cards. A yarn string moves down daily to track progress against schedule. This visual system lets anyone-even visitors-understand project status in seconds.
Chapter 6
Finding and Growing the Right People
The hiring process is critical for building a joyful culture, yet most companies get it catastrophically wrong. Traditional interviews involve mutual deception, followed by unprepared first days and broken promises that quickly demoralize new hires.
Menlo begins their interview process by inviting candidates on a public tour. If they see the collaborative environment-with no private desks or computers-and still want to work there, they have a better chance at cultural fit. They deliberately turn away lone-wolf "superstars" who hoard knowledge and damage team morale.
Traditional interviews-"two people lying to each other for two hours"-and polished resumes tell almost nothing about cultural fit. What matters most is whether someone has good kindergarten skills: Do they play well with others? Do they share? Can they collaborate effectively?
Their Extreme Interviewing process invites 30-50 candidates simultaneously, eliminating the need to sort through stacks of resumes. These high-energy mass interviews happen 2-3 times yearly. They arrange tables like speed-dating sessions and immediately immerse candidates in their culture. They're completely transparent about their values and process.
In the first interview round, candidates pair with each other on paper-based exercises while Menlo team members observe. They tell them their goal is to make their partner look good-a concept that immediately challenges traditional interview mindsets. Through three twenty-minute pairing exercises with different partners, candidates work on tasks like estimating project hours or designing screens. Observers watch for collaboration skills, asking themselves: "Would I like to pair with this person for a week? Would they support me if I struggled? Would I learn from them?"
After candidates leave, the team of observers discusses each interviewee for about five minutes. They vote with thumbs-unanimous up means immediate invitation to round two, unanimous down means rejection. Most votes are mixed, prompting discussions that reinforce cultural values. As CEO, Rich's vote carries no more weight than anyone else's-he wants team members to own this process since they'll be the ones pairing with new hires.
Second-round candidates receive a one-day paid contract working on actual client projects. They pair with Menlo team members who evaluate not just technical skills but curiosity and ability to learn on the fly. At day's end, they ask their pair partners a critical question: "Would you like to pair with this person again?" Positive feedback leads to a three-week paid trial, after which successful candidates join the team.
Despite their best efforts, hiring doesn't always work out as hoped. When they must let someone go, they do so with dignity and respect. Their policy is clear: if it didn't work out, you can try again. They're a birdcage without bars. Some candidates interview multiple times before joining, others come and go before realizing Menlo isn't the right fit, and some leave only to return later.
While programmers make up about half their team, creating beautiful software requires more than just coding. They need quality advocates who keep the big picture in mind, project managers who organize everything and serve as client contacts, and critically, their High-Tech Anthropologists (HTAs)-a role missing from almost every other software team that makes all the difference in delighting users.
Chapter 7
Understanding Users Through High-Tech Anthropology
The essence of joy at Menlo comes from delighting users with their software. Their goal is to create programs that are usable without manuals, training, or help text-even in domains where they have no prior experience.
The fundamental problem with most software is the disconnect between creators and users-they speak different languages and live in different worlds. On one side are the technical people (Homo logicus) who understand CPUs, RAM, and programming languages. On the other side are the "stupid users" who've been conditioned to blame themselves when technology doesn't work intuitively. The missing link between these groups is anthropology-studying people in their native environment to bring them utility and joy.
High-Tech Anthropology begins with understanding users in their native environment, as design is contextual. Focus groups don't work because of dominant personalities, and simply asking users what they want fails because they're unconsciously competent at their jobs. For a wedding planning website, HTAs would observe people in relevant locations-churches, bridal shows, jewelry stores-conducting casual observations and interviews. From these findings, they create "personas"-composite characters representing different user types.
The critical step is forcing clients to choose ONE primary persona as the design focus. Despite resistance ("We want this to work for everyone!"), they insist on prioritizing, using a target board with concentric rings to place the primary persona in the bull's-eye and secondary personas in outer rings. Every feature is then evaluated through the lens of the primary persona, making their work personal rather than abstract.
Their most successful HTA experience was with Accuri's flow cytometer project. Initially, they wanted all personas in the center of the target, but Menlo insisted they choose one. They reluctantly selected Emily, a lab director who wouldn't let her graduate assistant Brad use existing flow cytometers due to the high cost of errors. When Menlo suggested making the software easy enough for Brad to use, they initially resisted strongly. After reflection, they realized there were ten times more Brads than Emilys in the market. By switching to Brad as the primary persona, they created software accessible to this larger user base. Within three years of launch, Accuri became a formidable competitor and was sold for $205 million.
HTAs' observational skills have repeatedly proven invaluable. When designing a diesel motor diagnostic tool, they noticed mechanics wore rubber gloves-a crucial detail their client had missed despite thirty years in the industry. Their planned capacitive touch screen wouldn't work with gloves, so they switched to a resistive screen that responds to pressure.
HTAs work in pairs to create simple, low-fidelity, hand-drawn screen mock-ups sized to match the intended device. For hardware that doesn't yet exist, they build physical prototypes from materials like duct tape and cardboard. These paper-based prototypes are tested with real users, who they observe completing actual tasks rather than just asking for opinions. The crude, non-threatening nature of these prototypes encourages honest interaction.
Chapter 8
Creating a Culture of Experimentation and Safety
Fear kills joy. Creating safety is essential for innovation-people must feel secure enough to experiment without fear of consequences. Most organizations claim to value "failing fast," but quickly crush the spirit of teams testing their limits, resulting in "safe" experiments guaranteed to succeed but devoid of innovation.
For a "make mistakes faster" culture to thrive, you need fast, frequent, and inexpensive experimentation. "Let's run the experiment" is one of Menlo's most common phrases. They don't track success/failure rates, but if they did, they'd expect them to be roughly even-if failures dropped too low, they'd worry that fear had crept in and people weren't taking important risks.
At Menlo, programming pairs will experiment with code and willingly discard it if it doesn't work-a simple practice that challenges the powerful sunk-cost mentality. Sunk-cost thinking paralyzes organizations in three deadly ways: first, "We've invested too much in our current system to change it"; second, avoiding experiments for fear of wasting time or being seen as someone who tries things that fail; and third, refusing to change course even when an experiment is clearly failing, doubling down rather than accepting the loss.
When management manufactures artificial fear-whether through raised executive eyebrows at bad news or creating environments where "failure is not an option"-it amplifies sunk-cost thinking. Bad news goes underground but doesn't disappear, sometimes with catastrophic results as in the Challenger disaster. At Menlo, they've created a cultural HVAC system that pumps fear out, filters ambiguity, adjusts cultural temperature, and pumps safety back in.
To combat scope creep from a product manager who consistently requested more than forty hours of work per resource, James suggested a simple visual experiment: folding task cards proportionally to their time estimates (a full card representing 16 hours, folded once for 8 hours, twice for 4 hours, etc.). The team created tabloid-size planning sheets with boxes that could hold exactly forty hours worth of folded cards. This tangible representation forced the product manager to make real tradeoffs-when requesting "just one more thing," he had to decide what to remove to make room.
The joy in running small experiments comes from not having to make final decisions immediately-unambiguously modifying processes while reserving the right to change course later. With the large Wilmut medical device project involving over twenty people, the team struggled with weekly kickoff sessions. They experimented with splitting into smaller groups, with some team members initially resistant. The team embraced change by agreeing to try ideas for 2-3 weeks before judging results, recognizing that new processes are always bumpy at first.
When clients visited during Menlo's daily standup meetings, James suggested including them in the circle rather than making them awkward observers. Though initially uncertain how clients would react, the team invited them to join, passing the Viking helmet token to them when it was their turn to report. Clients embraced the practice, sharing their own work progress, challenges, and needs.
Menlo's baby experiment began with Tracy bringing baby Maggie to work daily. When Tracy worried about disruption, Rich reassured her: "I trust you. You're the mom... If there are problems, you'll do the right thing." Maggie became a joyful addition to their culture for four months, confirming that no experimental idea was too crazy. Rather than being disruptive, Maggie brought delight, with team members often competing to hold her when she fussed. Clients even behaved better in meetings with a baby present. This success led to more babies at Menlo, and they've won awards for supporting working parents.
Chapter 9
Leading with Vulnerability and Trust
Leadership at Menlo emerges naturally rather than through titles or position. When programmer Ian discovered unprofessional language in code before a holiday weekend, he not only reported it but volunteered to lead the investigation, demonstrating that leadership can come from anywhere. Rather than conducting a witch hunt, Rich created space for team members to step up.
When facing a challenging client who specialized in corporate culture evaluation but was exporting fear back to Menlo, the team asked Rich to intervene. Instead, he chose to stay away from the meeting, assuring his team he trusted them to represent Menlo's values. Though difficult for him, this restraint allowed the team to successfully handle the situation themselves. Michelle later expressed appreciation for Rich's trust and the authority to manage such situations.
As a leader, Rich acknowledges his team watches for inconsistencies, having been disappointed by leaders before. He admits to not having all answers and sometimes disappointing his team. The joyful path is creating a culture where decisions don't require his approval-team members simply inform him afterward.
Part of vulnerability is sharing ideas before they're fully formed-like Rich's personal 2018 vision he shared with the team in 2011, which included revenue projections, employee counts, and even personal details like grandchildren and vacation homes. By sharing early concepts, leaders let go of needing to be seen as the smartest person in the room, allowing ideas to improve through collaboration.
Menlo actively cultivates leadership by supporting team members' passions and initiatives. When Nate, a developer, created a programming summer camp for children to hack Minecraft using Python, the company provided space and encouragement. John M. demonstrated versatility by successfully transitioning between programming, High-Tech Anthropology, and project management roles, developing well-rounded leadership abilities through these experiences.
The team must sometimes stand firm with clients based on their expertise and observations, even risking being fired. Occasionally, Menlo must part ways with culturally incompatible clients-a difficult decision that reinforces their values despite financial implications. These challenging moments reveal the true strength of their intentionally joyful culture.
Chapter 10
Clarity, Sustainability, and Alignment
Rich recounts his chaotic experiences as VP at Interface Systems, where boardroom presentations of department goals were immediately undermined by hallway project management and scope creep from executives. His team's priorities were constantly hijacked through informal channels-even bowling leagues and after-work drinks-leaving him accountable for assignments he never approved.
Menlo eliminates hallway project management with a simple rule: nothing gets done unless first handwritten on a 512-by-812-inch index card. Each card includes the project code name, serial number, title, and description of how the work affects the software. Cards must be signed and dated by their authors-who can be any team member or even clients.
At Menlo, writing a card doesn't guarantee it will be worked on. Each story card must be estimated by those who'll do the work during weekly estimation sessions. After estimation, cards are photocopied and folded to sizes proportional to their time estimates using "Planning Origami." These folded cards are placed on planning tables alongside sheets representing the client's weekly budget.
After internal estimation, clients review the estimated cards and prioritize them through a planning game process. When a card makes it onto a planning sheet for the week, the client has officially authorized Menlo to work on it and bill for that work. Equally important, cards left on the table clearly won't be worked on. This visual system eliminates hallway project management where decisions are made in sidebar conversations without evaluation of their impact on existing priorities.
Sustainability at Menlo extends beyond environmental concerns to focus on sustaining the humans who work there. While Menlo has won multiple awards for workplace flexibility, they don't offer conventional flexibility like telecommuting or work-from-home options. They challenge the notion that providing company cell phones, laptops and VPN connections is "flexible"-it actually means expecting employees to be available 24/7.
Menlo maintains strict forty-hour workweeks, Monday through Friday with no weekends. This schedule allows team members time for sleep, family, hobbies, exercise and community involvement-making them more valuable as well-rounded innovators. The office typically closes by 6pm, with everyone starting with four weeks of vacation that doesn't expire.
The essence of a business is defined by three points: the world's outside perception, the inside reality for the team, and the heart of leadership. These must be in alignment for a healthy company. At Menlo, values are visible in action, not just hanging on a wall. Their openness, transparency, energy, and collaboration are immediately apparent to visitors. These values extend to their business dealings-their contracts are deliberately fair to both parties, unlike the one-sided agreements many companies offer.
This alignment creates remarkable efficiencies. They don't need a professional sales force because the community becomes their advocates-sending them the right clients who already understand their values. Similarly, recruiting happens naturally through professors who champion their approach and send them their best students. Their reputation generates press coverage no PR firm could afford to buy.
Chapter 11
Starting Your Own Journey to Joy
Organizational change often starts when people challenge invisible walls. Every organization needs a vision-a why that emanates from your heart. While some believe happiness follows success, author Shawn Achor teaches the opposite: success follows happiness. Rich believes success follows joy, which is even deeper than happiness.
Take time to describe your ideal day five years from now with rich detail. This vision should reflect both personal and work goals, showing what you want to feel rather than what you want to possess. Rich's own vision revealed his desire to be near family, create uncapped growth for Menlonians, and make a community impact.
Start exploring workplace joy through simple, free experiments. Try sitting among your team instead of in a private office-turn your old office into a conference room available to anyone. Experiment with standup meetings using a timer and a token. Or simply come visit Menlo to see their practices firsthand-you're welcome anytime.
Meaningful change is never easy. Choosing joy means embarking on an arduous journey comparable to climbing Mt. Everest. Changing human behavior is incredibly difficult yet potentially the most rewarding effort you'll undertake. There will be setbacks, and you'll need others to help when you falter. This journey to workplace joy is deeply personal-it transforms you into the person you've dreamed of becoming and draws others to your flame. Eventually, joy spreads throughout your team as everyone feels their own version of what you're feeling.
Thomas Edison's innovative work at Menlo Park provides the inspirational foundation for Rich Sheridan's company and approach. Edison wasn't focused on being first with the lightbulb but on making it practical and useful for everyone. His systematic approach to innovation and the culture he created in his "Invention Factory" changed the world in ways still felt today. Henry Ford preserved Edison's legacy by meticulously reconstructing the Menlo Park lab at Greenfield Village in Michigan, inspiring generations of young visitors-including an eight-year-old Sheridan who felt goosebumps walking through it.
On October 21, 1879, Thomas Edison lit an incandescent lightbulb in his Menlo Park laboratory. Though not the first to create a lightbulb, Edison pioneered a practical, sustainable version that could be widely adopted. He focused on building reliable systems for delivering light, requiring a special team and culture. This legacy continues today in the joyful workplace that Rich Sheridan has created-a modern invention factory where people come together to do their best work and find meaning in what they create.
