On a March morning in 1960, David Packard stood before a room of Hewlett-Packard managers and asked a question so elementary it bordered on provocation: "Why does a company exist in the first place?" The company he had cofounded twenty-one years earlier in a one-car garage at 367 Addison Street, Palo Alto — with $538 in working capital and a drill press mounted on a workbench — now employed thousands across multiple divisions and dominated the electronic test and measurement industry. Packard was not a philosopher. He was six-foot-five, broad-shouldered, a former Stanford varsity football and basketball player who still carried himself with an athlete's directness. Yet here he was, at the apex of commercial success, insisting that the purpose of all this enterprise was not, in fact, money. "I think many people assume, wrongly, that a company exists simply to make money," he told the room. "While this is an important result of a company's existence, we have to go deeper and find the real reasons for our being."
The speech was informal, unpolished, never intended for publication. It would not surface publicly for more than four decades — until Packard's son, David Woodley Packard, reproduced it as a full-page advertisement in the Wall Street Journal on March 15, 2002, as a pointed rebuke to then-CEO Carly Fiorina's proposed merger with Compaq Computer. The son believed his father's own words, "delivered on the job," constituted the best evidence for a business philosophy that Fiorina was about to destroy. That a dead man's unpublished speech could serve as the most potent weapon against a sitting CEO tells you something about the durability of what David Packard built. Not the oscillators, not the calculators, not the minicomputers or the laser printers — though those mattered — but the organizational architecture itself, the set of operating principles known simply as "the HP Way," which for half a century functioned as the closest thing American business had to a secular scripture.
This is the story of a man who built the template. The garage that became Silicon Valley. The management philosophy that Steve Jobs, among others, studied like Talmud. The fortune — Packard was worth roughly $4 billion at his death in 1996 — that he treated as an obligation rather than an achievement. And the paradox at the center of it all: that the man who articulated the most human-centered management philosophy of the twentieth century was, by most accounts, not particularly warm. He was reserved, plainspoken, occasionally intimidating, more comfortable discussing signal generator specifications than feelings. The HP Way was not the expression of a soft personality. It was the rigorous engineering of a system for getting the best out of people — designed by someone who understood systems better than sentiment.
Part IIThe Playbook
David Packard operated for more than half a century at the intersection of technical excellence and organizational design. The principles below are distilled from his speeches, his management practices, his financial decisions, and the culture he engineered at HP. They are not motivational platitudes. They are operating specifications for a system that worked.
Table of Contents
1.Define the purpose before the product.
2.Finance freedom with retained earnings.
3.Only enter markets where you can be distinctively better.
4.Design the organization for human scale.
5.Replace control with objectives.
6.Build information systems that bypass hierarchy.
7.Treat culture as infrastructure, not decoration.
Constrain growth to preserve character.
In Their Own Words
Why are we here? I think many people assume, wrongly, that a company exists solely to make money. Money is an important part of a company's existence, if the company is any good. But a result is not a cause. We have to go deeper and find the real reason for our being.
Take risks. Ask big questions. Don't be afraid to make mistakes; if you don't make mistakes, you're not reaching far enough.
The best possible way to prepare for tomorrow is to concentrate with all your intelligence, all your enthusiasm, on doing today's work superbly today.
Innovation is everything. When you're on the forefront, you can see what the next innovation needs to be.
Marketing is too important to be left to the marketing department.
The betterment of society is not a job to be left to a few. It's a responsibility to be shared by all.
More organizations die of indigestion than starvation.
Profit is not the proper end and aim of management – it is what makes all of the proper ends and aims possible.
To remain static is to lose ground.
The greatest success goes to the person who is not afraid to fail in front of even the largest audience.
The job of a manager is to support his or her staff, not vice versa and that begins by being among them.
Corporate reorganizations should be made for cultural reasons more than financial ones.
By the Numbers
The Hewlett-Packard Company Under Packard
$538Initial capital investment, 1939
$31BAnnual revenues at Packard's death, 1996
~$4BPackard's estimated personal fortune at death
57 yearsYears of active involvement with HP (1939–1996)
1stProduct sold to Walt Disney Studios for Fantasia
4Presidential 'E' awards for wartime efficiency
1989Year HP garage designated California Historic Landmark
Pueblo, Colorado, and the Education of Appetite
David Packard was born on September 7, 1912, in Pueblo, Colorado — a steel town on the Arkansas River, about as far from the future Silicon Valley as the American West could arrange. His father, Sperry Sidney Packard, practiced law. His mother, Ella Graber Packard, taught high school. The household was upper-middle-class and stable, which is to say it provided the kind of security that allows a child to develop obsessions without interruption.
Packard's obsession arrived early: electricity. He devoured library books on the subject, built his first radio while still in elementary school, and spent hours tinkering with crystal sets and amateur radio equipment. By the time he decided, as a grade-schooler, that he would become an engineer, the decision had the quality of discovery rather than aspiration — less "what I want to be" than "what I already am." At Centennial High School, he stood out in two dimensions that would define him for life: technical aptitude and physical scale. The six-foot-five teenager played football and basketball, excelled in science courses, and participated in amateur radio clubs. The combination — the enormous physical presence, the quiet technical competence, the team sports — would prove prophetic. Packard would build his entire management philosophy around the idea that individual talent, properly supported, could achieve collective goals. He learned that first on the field, not in a classroom.
In 1930, Packard enrolled at Stanford University as an electrical engineering student. The timing was brutal — the Depression was deepening — but Stanford in the early 1930s offered something that no amount of economic despair could diminish: Frederick Terman.
The Professor Who Manufactured a Valley
Frederick Emmons Terman — the man who would later be called, alongside William Shockley, the "father of Silicon Valley" — was in 1930 a young professor of electrical engineering at Stanford with an unusual conviction. Where most engineering faculty of the era maintained a gentleman's distance between academic research and commercial application, Terman actively encouraged his students to bridge the gap. He believed that the future of the West Coast depended on its ability to develop technology industries that could compete with the industrial East, and he saw Stanford as the incubator. His approach was practical, mentorship-driven, and profoundly at odds with the academy's growing preference for theoretical abstraction over applied problem-solving.
Terman noticed Packard immediately. The young Coloradan combined genuine intellectual ability — he was elected to Phi Beta Kappa — with something rarer: a builder's instinct. He didn't just want to understand circuits. He wanted to make things. Terman also introduced Packard to another student who shared this disposition: William Redington Hewlett, a San Francisco native whose father was a professor at Stanford's medical school. Hewlett was smaller, more gregarious, and possessed a particular genius for negative feedback circuits that complemented Packard's administrative and engineering strengths. The two became fast friends — hiking, fishing, and talking electronics with the ease of men who had found their natural frequency.
Packard graduated with his bachelor's degree in 1934 and, after a brief stint at the University of Colorado, moved to Schenectady, New York, to work in General Electric's vacuum tube engineering department. It was decent work at a great company, and it paid well. But by 1938, Terman had lured him back. The professor offered Packard a research assistantship, a path to a graduate degree, and — crucially — proximity to Hewlett, who had been developing his ideas on oscillator design. The effective pay cut was more than 50%. Packard took it without hesitation, returning to Palo Alto with the woman he would marry that year: Lucile Salter, a Stanford graduate who would become HP's first employee, serving as secretary and bookkeeper in the years when the company's entire workforce could gather around a kitchen table.
I think it is obvious that we started this company because Bill and I, and some of those working with us in the early days, felt that we were able to design and make instruments which were not as yet available. I believe that our company has grown over the years for that very reason. Working together we have been able to provide for the technical people, our customers, things which are better than they were able to get anywhere else. The real reason for our existence is that we provide something which is unique.
— David Packard, speech to HP managers, March 8, 1960
$538 and a Coin Toss
The founding of Hewlett-Packard in 1939 is the original Silicon Valley creation myth, and like all myths it has been polished by repetition until the edges gleam. The garage at 367 Addison Street. The $538 in working capital. The coin toss that determined whether the company would be called Hewlett-Packard or Packard-Hewlett. The early product line — a grab bag of custom electronic equipment including air conditioning controllers, foul-line indicators for bowling alleys, an electronic harmonica tuner, and, most improbably, exercise machines. It reads like a comedy of ambition, two young engineers taking any order that walked through the door, and there's truth in that. But the garage period also established the first axiom of what would become the HP Way: start with what you can do, and let the market tell you what you should do.
What they should do, it turned out, was build audio oscillators. Hewlett had developed a design for a resistance-capacitance audio oscillator — the Model 200A — that was simpler, more stable, and dramatically cheaper than anything else on the market. Priced at $54.40, it undercut comparable instruments that cost $200 or more. The 200A (so numbered because "Model 1" sounded too amateurish) caught the attention of Bud Hawkins, a sound engineer working on Walt Disney's Fantasia. Disney Studios purchased eight units — the Model 200B, a slightly refined version — for $71.50 each, to use in the development of the film's pioneering multi-channel sound system. Total revenue: $572. The company's first substantial sale, and it came from an industry they had never targeted.
The lesson Packard absorbed was not about audio oscillators or the entertainment industry. It was about the relationship between technical contribution and commercial success. If your product was genuinely better — more accurate, more reliable, less expensive — the customers would find you. You didn't need to sell harder. You needed to build better. This conviction would calcify into doctrine: HP would only enter markets where it could make a distinctive technical contribution. No me-too products. No competing on price alone. The corollary, which Packard would enforce for decades, was equally rigid: if a product line no longer represented a genuine technical advance, HP should exit the business, even if it was profitable.
By 1940, the company had ten employees, annual sales of roughly $30,000, and had outgrown the garage. A decade later, revenues reached approximately $700,000. Another decade after that — 1957 — the company went public with annual sales around $30 million. The growth curve was steep but controlled, and the control was deliberate. Packard and Hewlett financed expansion almost entirely from retained earnings, refusing to take on significant debt. "Pay as you go" was not a slogan; it was a financial constraint that shaped every strategic decision the company made for its first four decades. When Packard finally articulated why in 1960, the reasoning was characteristically blunt: debt creates obligations to creditors, and obligations to creditors compromise your freedom to serve customers and employees.
War, Peace, and the Discipline of Contraction
World War II transformed Hewlett-Packard from a small instrument company into a defense contractor, but the transformation was not the kind that required a new identity. The military needed precisely the kind of electronic test and measurement equipment HP already made — signal generators, wave analyzers, instruments for radar, sonar, and aviation — and HP delivered them with such efficiency that the company received the government's "E" for Efficiency award on four separate occasions, an extraordinary production record.
Packard ran the company almost single-handedly during the war. Hewlett had entered the U.S. Army, eventually serving as head of the electronics section in the New Developments Division of the War Department. It was the first sustained test of Packard as sole administrator, and he passed it in a way that revealed his defining quality: the ability to build systems that worked without him. The wartime HP was not a one-man show. It was an organization of people who understood their objectives and had the freedom to pursue them. The phrase "management by objective" had not yet been coined, but the practice was already in place.
What happened after the war was more instructive. Government contracts evaporated. Revenue collapsed. Companies across the defense sector laid off workers in droves. Packard did too — he had no choice — but the experience left a permanent mark. He became obsessed with building a financial structure that could absorb shocks without forcing the company to abandon its people. The "pay as you go" philosophy intensified. HP would grow only as fast as its own earnings permitted. It would maintain cash reserves sufficient to survive downturns. It would diversify its product line so that no single contract or customer could determine its fate. These were not conservative instincts dressed up as principles. They were the conclusions of a man who had watched the human cost of financial fragility and decided, with an engineer's precision, to design it out of the system.
Management by Walking Around, and the Architecture of Trust
The HP Way, as it came to be known, was not a single idea. It was a system of interlocking practices — some philosophical, some operational, some cultural — that functioned as the company's operating system. Packard did not write it down in one place; it accreted over decades, formalized partly in his 1960 speech, partly in corporate objectives documents, partly in oral tradition, and eventually in his memoir, The HP Way: How Bill Hewlett and I Built Our Company, published in 1995, a year before his death. But the core principles were present from the beginning:
A company exists to make a technical contribution, not merely to make money. The best results come when you get the right people, trust them, give them freedom to find the best path to achieve objectives, and let them share in the rewards their work makes possible. Every employee deserves to be treated with respect and dignity. Integrity is non-negotiable. A company has an obligation to the communities in which it operates.
The most famous operational expression of these principles was "management by walking around" — MBWA — the practice of managers leaving their offices to talk with workers on the factory floor, in the labs, at their desks. The phrase became so widely adopted that it entered the general lexicon of American management, eventually losing its specificity through overuse. But at HP, MBWA was not a technique. It was an information system. Packard understood, with an empiricist's clarity, that formal reporting structures filter and distort information as it moves upward through an organization. The only way to know what was actually happening — the quality problems, the morale issues, the breakthrough ideas that hadn't yet survived the journey through middle management — was to go look. Not on a scheduled tour with an entourage, but casually, repeatedly, with genuine curiosity.
The companion practice was the open-door policy, which at HP meant something specific: no closed offices. The workspace was designed so that managers were physically accessible. Combined with MBWA, this created an environment in which hierarchy existed — Packard was not naive about the necessity of authority — but hierarchy was permeable. A recent graduate could tell a general manager to wait ten minutes while a build finished compiling, and the general manager would smile and come back later. That story, told by a former HP employee, carries the weight of lived experience: "Those of us who knew the manager were aghast and assumed the grad would be in for a bit of a tough time. But the GM just smiled and said 'of course, hope it compiles OK,' went away, and came back later."
This was not accidental kindness. It was engineered culture. Packard designed HP's management system around a specific theory of human motivation: that people do their best work when they understand what they're trying to achieve, have the freedom to figure out how to achieve it, and feel that their contribution matters. "Management by objective as compared to management by control," he called it. The distinction was not rhetorical. Management by control — the military model, the assembly-line model — assumed that workers needed to be told precisely what to do and monitored for compliance. Management by objective assumed that workers needed to understand the goal and be trusted to find the path. The entire organizational architecture of HP followed from this distinction: decentralized divisions, minimal corporate bureaucracy, profit sharing, stock purchase plans, flexible working hours, and a tradition of promoting from within that made the company feel, even as it grew to tens of thousands of employees, like a meritocracy that remembered your name.
Supervision is not a job of giving orders; it is a job of providing the opportunity for people to use their capabilities efficiently and effectively.
— David Packard, speech to HP managers, March 8, 1960
The Division Structure and the Genius of the And
As HP grew, Packard faced the quintessential scaling problem: how do you preserve the intimacy and agility of a small company within a large organization? His answer was aggressive decentralization. HP organized itself into small, semi-autonomous divisions — each with its own engineering, manufacturing, and marketing functions — that operated almost like independent businesses within a shared corporate framework. No division was allowed to grow so large that its managers lost touch with the people doing the work. When a division reached a size threshold — roughly 1,500 employees — it was split.
The division structure was Packard's engineering solution to a human problem. He believed that innovation and commitment flourished in small groups where individuals could see the connection between their effort and the outcome. Large organizations, by contrast, bred bureaucracy, anonymity, and the insidious sense that no single person's contribution mattered. By keeping divisions small, HP maintained the startup's intensity within the corporation's scale. Each division had its own profit-and-loss responsibility, which meant each had the autonomy to make decisions quickly and the accountability to make them well.
Jim Collins, the management writer who studied HP extensively, identified the underlying logic as "the genius of the And" — the refusal to accept false trade-offs. Make a technical contribution and meet customer needs. Take care of your people and demand results. Set unwavering standards and allow immense operating flexibility. Achieve growth and achieve profitability. Behind these specifics lay what Collins called "the biggest 'And' of all": preserve the core and stimulate progress. HP under Packard was simultaneously one of the most principled and one of the most innovative companies in America, and Packard saw no contradiction between those qualities. Principle was not a brake on innovation. It was the track.
The financial discipline deserves emphasis because it was so unusual. HP, under Packard, grew for decades without significant debt. The company funded its expansion from profits — an approach that Wall Street analysts occasionally criticized as excessively conservative but that gave HP a freedom its leveraged competitors could not match. In downturns, HP did not have to slash R&D to service debt. In boom times, HP did not have to dilute shareholders to fund growth. The retained-earnings model was slower, but it was resilient. And resilience, for Packard, was not just a financial quality. It was a moral one. A company that could survive adversity without betraying its people or its principles was, in his view, the only kind worth building.
The Pentagon Interlude
In January 1969, President Richard Nixon appointed David Packard as U.S. Deputy Secretary of Defense — the number-two position in the largest bureaucratic organization on Earth. Packard was not a political creature. He was a registered Republican with moderate instincts, a large donor, and a man whose reputation for candor and administrative competence made him an obvious choice for an administration that wanted to signal seriousness about defense reform. The appointment required Packard to place his HP shares — worth an extraordinary sum — in a charitable trust, effectively removing him from active management of the company he had built over thirty years.
The Pentagon was, in almost every respect, the anti-HP. It was the world's largest management-by-control organization: hierarchical, process-obsessed, politically compromised, and chronically incapable of delivering weapons systems on time or on budget. Packard arrived with the engineer's conviction that these problems were not inevitable but designed — the natural consequence of procurement processes that prioritized political considerations over technical ones, that rewarded cost overruns rather than punishing them, and that separated the people making decisions from the people affected by those decisions.
He pushed for reforms: "fly before you buy" testing philosophies, greater reliance on competitive prototyping, and what he called "milestone management" — defining clear performance milestones that programs had to meet before receiving additional funding. Some reforms stuck. Many didn't. The military-industrial complex had a half-century head start on institutional inertia, and two and a half years was not enough to overcome it. Packard resigned in December 1971, returned to HP as chairman of the board in 1972, and spent the rest of his life serving in various advisory capacities on defense matters, including chairing President Reagan's Blue Ribbon Commission on Defense Management (the "Packard Commission") in 1985–86. The commission's recommendations — many of which echoed what Packard had tried to implement fifteen years earlier — became the basis for significant procurement reforms in the Goldwater-Nichols Defense Reorganization Act.
The Pentagon years revealed something about Packard that the HP years had only suggested: his willingness to enter systems he found dysfunctional and attempt to fix them from the inside, even when the probability of success was low. He was not a revolutionary. He was a reformer — patient, methodical, willing to spend political capital on process improvements that would never generate headlines. The approach was identical to his management philosophy at HP: define the objective, hire competent people, give them authority, hold them accountable, and resist the urge to micromanage. That it worked brilliantly in Palo Alto and only fitfully in Washington tells you less about the philosophy than about the difference between organizations that are built on trust and organizations that are built on power.
The Things He Refused to Build
The negative space of HP's history — the businesses Packard chose not to enter, the acquisitions he did not make — reveals as much about his philosophy as the products the company shipped. HP under Packard and Hewlett was conspicuously absent from consumer electronics, despite possessing the technical capability to compete. It avoided commodity markets where the only differentiator was price. It stayed out of defense contracting as a primary business, even after Packard's Pentagon experience gave him unmatched insight into the market's dynamics. The principle was always the same: HP should only be in businesses where it could make a distinctive technical contribution. If the company couldn't be the best — not just competitive, but genuinely, measurably better — then it had no business being there.
This discipline extended to personnel. Packard was famous for a hiring philosophy that prioritized cultural fit and intrinsic motivation over raw credentials. He wanted people who were driven by the work itself, not by the paycheck. "You know that those people you work with that are working only for money are not making any real contribution," he told the HP managers in 1960. The statement sounds harsh, but Packard meant it descriptively rather than morally. His management system was designed around the assumption that workers wanted to contribute. If someone was only in it for the money, the system's benefits — autonomy, trust, shared rewards — would be wasted, and the system itself would be degraded.
The most dramatic expression of restraint came in HP's approach to growth. Packard and Hewlett imposed what amounted to a self-limiting principle: the company would grow only in areas where it could maintain its culture and its technical standards. Growth for its own sake was explicitly rejected. "Our company has grown over the years," Packard said, but he attributed that growth not to ambition but to capability — "because Bill and I felt that we were able to design and make instruments which were not as yet available." The passive construction is telling. Growth happened to HP because it did good work. HP did not pursue growth as an objective.
This philosophy would be tested after Packard's death in ways he could not have anticipated, and it would fail — spectacularly.
What Happened After
David Packard died of pneumonia on March 26, 1996, at Stanford University Hospital in Palo Alto. He was eighty-three years old. HP at his death had roughly $31 billion in annual revenues and was one of the most admired companies in the world. His will directed the bulk of his fortune — an estimated $4 billion — to the David and Lucile Packard Foundation, which he had established with his wife in 1964 and which would become one of the largest philanthropic organizations in the United States, funding conservation, science, population research, and children's health, including the Lucile Salter Packard Children's Hospital at Stanford and the Monterey Bay Aquarium, which Packard had personally helped design and which became one of the most important marine research institutions in the world.
The company he left behind did not survive his philosophy for long. In 1999, the HP board hired Carly Fiorina — a charismatic outsider from Lucent Technologies with no engineering background — as CEO. Fiorina's signature move, the $25 billion acquisition of Compaq Computer in 2002, was the kind of deal Packard would have found incomprehensible: a merger driven by scale rather than technical contribution, designed to compete in the commodity PC market that HP had historically avoided. The deal was bitterly contested. Walter Hewlett, Bill's son, led the opposition. David Woodley Packard, David's son, published his father's 1960 speech as a full-page Wall Street Journal ad in an attempt to remind the board — and the public — what HP was supposed to be. The merger passed by a razor-thin margin of 51.4% to 48.6%.
What followed was a decade-long cascade of self-inflicted wounds that would have been comic if the human cost had not been so severe. A pretexting scandal in which a board member, an executive, and HP-paid investigators faced criminal charges for spying on journalists. The $1 billion acquisition of Palm Computing in 2010, followed by the sale of Palm's intellectual property. The $13.9 billion purchase of EDS in 2008 and the $11 billion acquisition of Autonomy in 2011, each resulting in $8 billion write-downs. The hiring of Leo Apotheker as CEO in September 2010, followed by his firing a year later. The leak of plans to sell the PC business, followed by Meg Whitman's declaration that HP was "better together," followed by her reversal, followed by the 2015 split into two publicly traded companies — Hewlett Packard Enterprise and HP Inc. — ending seventy-six years of existence as a single entity.
The irony is almost too neat to bear. The company whose founder insisted it existed "to make a contribution to society" spent the two decades after his death making contributions primarily to the field of management failure case studies. Every misstep violated a specific Packard principle: acquisitions for scale rather than technical contribution. Leadership by outsiders who didn't understand the culture. Growth pursued as an objective rather than a consequence. Debt taken on to finance deals that should never have been made. The HP Way, it turned out, was not self-sustaining. It required the people who believed in it to be in charge. When they weren't, the system did not degrade gracefully. It collapsed.
The Builder's Paradox
There is a passage in Walter Isaacson's biography of Steve Jobs that places Packard in a particular constellation:
"He had neither Ellison's conspicuous consumption needs nor Gates' philanthropic impulses nor the competitive urge to see how high on the Forbes list he could get. Instead, his ego needs and personal drives led him to seek fulfillment by creating a legacy that would awe people. A dual legacy, actually, building innovative products and building a lasting company. He wanted to be in the Pantheon with, indeed a notch above, people like Edwin Land, Bill Hewlett and David Packard."
Isaacson is writing about Jobs, but the passage inadvertently reveals what Packard meant to the generation that followed: not a personality to emulate but a standard to exceed. Jobs, who had called HP at age twelve to ask for spare parts for a frequency counter and been invited by Hewlett himself to work a summer on the assembly line, understood that Packard's achievement was not any particular product but the institution itself. The product was the company. The company was the product.
Packard would have found the comparison uncomfortable. He was not in the mythology business. His eleven rules for getting along with others, first presented at HP's second annual management conference in 1958, began: "Think first of the other fellow. This is THE foundation — the first requisite — for getting along with others." The rules are elementary, almost naive — build up the other person's sense of importance, give sincere appreciation, eliminate the negative, try to understand the other person. They read like something from a Dale Carnegie seminar, and Packard would not have been embarrassed by the comparison. He believed that management was fundamentally about human relationships, and that the principles governing good relationships were simple, well-known, and chronically ignored. His contribution was not to discover these principles but to encode them into the architecture of a major corporation — to make them structural rather than aspirational, to prove that a company could be simultaneously humane and excellent, generous and demanding, principled and wildly profitable.
Think first of the other fellow. This is THE foundation — the first requisite — for getting along with others. And it is the one truly difficult accomplishment you must make. Gaining this, the rest will be "a breeze."
— David Packard, HP management conference, 1958
The David and Lucile Packard Foundation, by the mid-2000s, held assets exceeding $5 billion. The Monterey Bay Aquarium Research Institute, which Packard had founded in 1987 to conduct deep-sea research, launched in 2025 a state-of-the-art research vessel — the R/V David Packard, a 164-foot monohull designed for remotely operated vehicle operations with a range of 4,300 nautical miles. The HP garage at 367 Addison Street had been designated a California Historical Landmark and was widely described as "the birthplace of Silicon Valley." The Stanford Theatre in downtown Palo Alto, restored in the 1980s by his son David Woodley Packard, still used analog technology to show classic films from the 1920s through the 1960s.
The company itself had fractured into pieces — HP Inc., Hewlett Packard Enterprise, Agilent Technologies, Keysight Technologies — each carrying a fragment of the original DNA but none carrying the whole. The HP Way lived on as a management case study, invoked in business school classrooms and leadership podcasts and Substack newsletters, its principles simultaneously acknowledged and violated by the very industries Packard had helped create. Silicon Valley in the twenty-first century — the culture of move fast and break things, of growth at all costs, of founder worship and employee disposability — would have been alien to him. Not because he was sentimental, but because it was bad engineering. Systems designed without concern for the people inside them produce unreliable results. Packard knew this. He proved it for fifty-seven years. The proof, like most proofs, has not prevented the error from recurring.
In Pueblo, Colorado, Centennial High School still stands. The library where a boy once read every book on electricity has been renovated and renamed. The boy became the man who built the garage that built the valley that built the future, and the future forgot how the garage worked. All that remains of the original architecture — the real architecture, the human one — is a speech, never meant for publication, in which a tall engineer stood before a room of managers and asked them to remember why they were there.
8.
9.Share the rewards structurally, not symbolically.
10.Encode the philosophy so it survives the founder.
11.Use restraint as a competitive weapon.
12.Serve the institution, not the ego.
Principle 1
Define the purpose before the product.
Packard's insistence that a company exists to make a contribution rather than to make money was not philosophical decoration. It was a decision-making framework. Every product decision, every market entry, every organizational choice at HP was filtered through a single question: does this represent a genuine technical contribution? The question functioned as a constraint — it eliminated entire categories of opportunity that other companies pursued — but constraints, in engineering, are what give a system its shape. Without the contribution test, HP would have been a different company: larger, perhaps, but less focused, less coherent, and less durable.
The purpose framework also solved a motivation problem that plagues organizations at scale. When a company defines itself by its profit targets, every employee's motivation is mediated through money — an extrinsic reward that research consistently shows is a weaker driver of creative work than intrinsic satisfaction. When a company defines itself by its contribution, every employee has access to a richer motivational source: the knowledge that their work matters. Packard understood this intuitively. "The individual who is doing a worthwhile job is working because he feels he is accomplishing something worthwhile," he said. The purpose was not just a message to shareholders. It was an architecture for motivation.
Tactic: Before launching any new initiative, articulate in one sentence the specific contribution it makes — to customers, to the field, to the community — that would not exist without it. If you cannot write that sentence, do not launch the initiative.
Principle 2
Finance freedom with retained earnings.
HP's "pay as you go" financial philosophy — funding growth almost entirely from retained earnings rather than debt — was the structural foundation of every other principle in the HP Way. Without financial independence, the trust-based management system would have been impossible: creditors impose conditions, conditions constrain freedom, and constrained freedom undermines the autonomy that Packard believed was essential to both innovation and human dignity.
The retained-earnings model imposed a natural speed limit on growth, which Packard considered a feature rather than a bug. Companies that grow faster than their earnings can sustain are, in his view, building on a foundation that someone else controls. When the creditor's interests diverge from the company's — as they inevitably do in downturns — the company's people and principles become collateral damage. HP's financial conservatism was not timidity. It was the engineering of organizational resilience.
$
HP's Financial Architecture
How Packard's financial principles shaped HP's growth
Tactic: Before taking on any external obligation — debt, investor commitments, partnership terms — ask: does this obligation constrain our freedom to serve our people and our purpose in a downturn? If yes, find another way to fund it.
Principle 3
Only enter markets where you can be distinctively better.
The contribution test was not just a purpose statement. It was a market selection tool. HP under Packard entered a market only when it could offer something that was measurably superior — more accurate, more reliable, more convenient, less expensive — than what existed. This sounds obvious. It is not. Most companies enter markets because the market is large, because competitors are profitable, because the board demands growth in new segments. Packard's standard was different: not "can we compete?" but "can we contribute?"
The practical effect was a portfolio of products and businesses that were, individually, among the best in their categories. HP's signal generators, counters, audio oscillators, and vacuum tube voltmeters captured dominant market shares not because HP outspent competitors on sales and marketing but because the products were better. The contribution test also functioned as an exit criterion: when a product line no longer represented a genuine advance, HP had the discipline — rare in any organization — to let it go.
Tactic: For every product in your portfolio, answer honestly: would our customers be meaningfully worse off if this product disappeared? If the answer is no, you are consuming resources that should be allocated to something that matters.
Principle 4
Design the organization for human scale.
Packard's division structure — small, semi-autonomous units with their own engineering, manufacturing, and marketing functions — was his answer to the fundamental tension of organizational growth: scale creates efficiency but destroys intimacy, and intimacy is where innovation and commitment live. By capping division size at roughly 1,500 employees and splitting divisions when they exceeded this threshold, Packard maintained the conditions under which individuals could see the connection between their work and its outcome.
This was not sentimentality. It was systems thinking. Packard understood that the feedback loops that drive performance — the cycle of effort, observation, adjustment, and improvement — degrade as organizations grow. In a small group, you can see the consequences of your decisions. In a large organization, consequences are diffused, delayed, and attributed to forces beyond anyone's control. Small divisions preserved the accountability that large organizations systematically destroy.
Tactic: When any team, division, or unit grows to the point where individuals can no longer see the impact of their work on the final product, split it. The overhead of duplication is cheaper than the cost of disengagement.
Principle 5
Replace control with objectives.
"Management by objective as compared to management by control" was Packard's shorthand for a radical proposition: that you could get better results by telling people what to achieve and letting them figure out how than by telling them precisely what to do and monitoring their compliance. The distinction sounds theoretical. At HP, it was operational. Managers were evaluated not on how closely they supervised their teams but on the results their teams produced. The implicit message — we hired you because you're competent, and we trust you to do your job — was simultaneously flattering and demanding. Freedom and accountability were not opposites. They were the same thing.
Packard was explicit about the failure mode he was designing against: "I have noticed when we promote people from a routine job to a supervisory position, there is a tremendous likelihood that these people will get carried away by the authority. They figure that all they have to do now is tell everyone else what to do and quite often this attitude causes trouble." The antidote was to redefine supervision as service: "Supervision is not a job of giving orders; it is a job of providing the opportunity for people to use their capabilities efficiently and effectively."
Tactic: Rewrite every manager's job description to focus on outcomes, not activities. Replace "oversee the completion of" with "ensure the team achieves." Then hold them accountable for the outcome, not the method.
Principle 6
Build information systems that bypass hierarchy.
Management by walking around was not a social ritual. It was an information architecture. Packard understood that formal reporting structures are, by their nature, information filters — each layer of management selects, summarizes, and sanitizes data before passing it upward. The result is that senior leaders make decisions based on information that has been optimized for their comfort rather than their effectiveness. MBWA was Packard's bypass: a direct connection between leadership and reality that no org chart could provide.
The open-door policy served the same function in the other direction: it gave employees a channel to surface problems, ideas, and concerns without having to navigate the chain of command. The combination — leaders who went to the work and workers who could go to the leaders — created a bidirectional information flow that most hierarchies lack. The emphasis on genuine curiosity was critical. MBWA degrades into theater the moment it becomes ritualistic or performative. Packard's injunction was to go listen, not to go be seen listening.
Tactic: Spend at least 20% of your working time in unscheduled, unstructured conversations with people doing the actual work. Bring questions, not answers. Track the ratio of time you spend transmitting information to time you spend receiving it.
Principle 7
Treat culture as infrastructure, not decoration.
Most companies treat culture as a communication problem — something to be articulated in mission statements, reinforced through posters and town halls, and measured through engagement surveys. Packard treated it as a design problem. The HP Way was not a set of values posted on a wall. It was embedded in the organizational structure (small divisions), the financial architecture (no debt), the physical environment (open offices), the compensation system (profit sharing, stock purchase plans), the hiring criteria (cultural fit over credentials), and the promotion practices (internal advancement). Culture, in Packard's system, was not what you said. It was what you built.
This distinction explains why the HP Way collapsed so quickly after Packard and Hewlett were no longer in charge. Culture-as-communication is fragile: it depends on continuous reinforcement by leaders who believe in it. Culture-as-infrastructure is more durable, but it can still be dismantled by leaders who don't understand it — or who understand it and choose to override it, as happened with the Compaq merger and the succession of outsider CEOs who followed.
Tactic: For every cultural value your organization claims, identify the structural mechanism that enforces it. If a value has no structural enforcement — no policy, no process, no design feature that makes it the default behavior — it is an aspiration, not a culture.
Principle 8
Constrain growth to preserve character.
Packard's self-limiting growth principle — that HP should grow only in areas where it could maintain its culture and technical standards — was perhaps his most counterintuitive contribution. In an economic system that rewards growth above all else, the decision to grow less requires extraordinary discipline and a willingness to disappoint shareholders, analysts, and the market.
Packard justified the constraint in engineering terms: growth beyond the organization's capacity to absorb it produces defects. In manufacturing, rapid scaling introduces quality problems. In management, rapid scaling introduces cultural problems — new hires who don't understand the values, managers who default to control because they don't have time to build trust, leaders who measure success by headcount rather than contribution. The constraint was not anti-growth. It was pro-quality. Packard wanted growth that strengthened the system rather than diluting it.
Tactic: Define the maximum rate at which your organization can grow without degrading its culture, its quality standards, or its ability to develop leaders internally. Make that rate your growth target, regardless of market demand.
Principle 9
Share the rewards structurally, not symbolically.
HP under Packard implemented profit sharing, stock purchase plans, and flexible working hours decades before these practices became standard in Silicon Valley. The critical distinction was that these mechanisms were structural — built into the compensation system, available to all employees, and tied to actual company performance — rather than symbolic gestures designed to generate goodwill without redistributing value.
Profit sharing, in particular, served a dual purpose. It aligned employees' financial interests with the company's success, creating the kind of intrinsic ownership that stock options in later Silicon Valley companies would attempt (with mixed results) to replicate. And it made the "contribution" philosophy tangible: if the company made a genuine technical contribution, customers bought the products, profits rose, and everyone benefited. The feedback loop between purpose and reward was direct and visible.
Tactic: Ensure that every employee has a financial mechanism — profit sharing, equity, bonus pool — that connects their personal outcome directly to the organization's collective performance. Symbolic rewards (pizza parties, verbal recognition) are supplements, not substitutes.
Principle 10
Encode the philosophy so it survives the founder.
The most important lesson of the HP story may be the one Packard failed to learn: that a management philosophy, no matter how brilliantly designed, does not survive the founder automatically. The HP Way was encoded in structures, practices, and traditions — but not in governance mechanisms that could prevent future leaders from dismantling those structures. When Fiorina arrived with a mandate for transformation, there was no constitutional protection for the principles that had made the company worth transforming.
Packard's 1960 speech, his 1958 rules, his memoir — these were the philosophical documentation. But documentation without enforcement is advisory, not binding. The structural equivalent of constitutional protection in a corporation is the board of directors, and HP's board, after Packard's death, proved inadequate to the task. The lesson is not that founder philosophies are inherently fragile — it is that encoding them requires deliberate governance design: board composition, bylaw provisions, cultural due diligence for leadership hires, and explicit criteria for evaluating strategic decisions against founding principles.
Tactic: If your organization has founding principles that matter, write them into governance documents — board charters, investment criteria, CEO evaluation frameworks — that give them structural force beyond any individual leader's tenure.
Principle 11
Use restraint as a competitive weapon.
The things HP chose not to do — consumer electronics, commodity markets, debt-financed acquisitions, growth for growth's sake — were not missed opportunities. They were strategic decisions that concentrated the company's resources on the areas where it could make the greatest contribution. Restraint freed capital, attention, and talent for work that mattered.
In a competitive landscape where most companies defined strategy as the selection of opportunities to pursue, Packard defined strategy equally by the opportunities to decline. Every "no" was a resource allocation decision: every market HP didn't enter was engineering talent that went into products HP could dominate. Every acquisition HP didn't make was cash that stayed on the balance sheet, preserving the financial independence that made the HP Way possible. Restraint was not passive. It was the active engineering of focus.
Tactic: Maintain a "not-doing" list alongside your strategic plan. For every initiative you pursue, identify the initiatives you are explicitly declining and the resources that declination frees for your priorities.
Principle 12
Serve the institution, not the ego.
Packard was one of the wealthiest people in America. He did not act like it. He drove ordinary cars, lived modestly relative to his means, avoided the social circuits that other billionaires traveled, and poured the vast majority of his fortune into a foundation that funded conservation, science, and children's health. The National Science and Technology Medals Foundation described him as having "extraordinary and unselfish leadership." The New York Times called him "the first high-tech mogul." Both descriptions are accurate and both miss the point slightly: Packard was not selfless in the saintly sense. He was selfless in the engineering sense. He understood that his ego, if given primacy, would distort the system he had built.
The deepest expression of this principle was the name itself: Hewlett-Packard, not Packard-Hewlett. The order was determined by a coin toss — but Packard, the more administratively dominant of the two founders, never sought to change it. The company's identity was not an extension of his personal brand. It was a shared institution, built by many hands, belonging ultimately to the people who worked there and the communities it served. In an era of founder cults and CEO celebrity, this remains the most radical thing about David Packard: he built something magnificent and did not insist that it be about him.
Tactic: In every public communication, meeting, and strategic decision, ask: am I optimizing for the institution's long-term health or for my own visibility? When the two conflict — and they will — choose the institution.
Part IIIQuotes / Maxims
In their words
I think many people assume, wrongly, that a company exists simply to make money. While this is an important result of a company's existence, we have to go deeper and find the real reasons for our being. As we investigate this, we inevitably come to the conclusion that a group of people get together and exist as an institution that we call a company so they are able to accomplish something collectively which they could not accomplish separately. They are able to do something worthwhile — they make a contribution to society.
— David Packard, speech to HP managers, March 8, 1960
You know that those people you work with that are working only for money are not making any real contribution. I want to emphasize then that people work to make a contribution and they do this best when they have a real objective when they know what they are trying to achieve and are able to use their own capabilities to the greatest extent.
— David Packard, speech to HP managers, March 8, 1960
Give sincere appreciation. If we think someone has done a thing well, we should never hesitate to let him know it. WARNING: This does not mean promiscuous use of obvious flattery. Flattery with most intelligent people gets exactly the reaction it deserves — contempt for the egotistical "phony" who stoops to it.
— David Packard, HP management conference, 1958
HP's success is due to the talents and dedication of you and your colleagues and of the people who have gone before you. Together we have built a truly remarkable company. I believe it is a company without peer.
— David Packard, in a message to HP employees, 1995
During the corrosive debate over the Compaq merger, the HP leadership at the time persistently portrayed itself as doing exactly "what Dave Packard would have done." As an antidote to this dubious clairvoyance, I published a full-page ad in the Wall Street Journal reprinting a wonderful speech my father gave in 1960 to a group of HP managers. My father's own words, delivered on the job, seemed to me the best evidence for his business philosophy.
— David Woodley Packard, foreword to The HP Way, 2005
Maxims
Contribution before profit. A company that cannot articulate the specific contribution it makes to its customers and community has no reason to exist, regardless of its financial performance.
Fund your freedom. Debt is not just a financial instrument; it is a transfer of decision-making authority from the people inside the organization to the people outside it. Avoid it.
The product is the company. Hewlett and Packard's greatest creation was not the audio oscillator or the pocket calculator — it was HP itself. Build the institution with the same rigor you bring to the product.
Supervision is service, not authority. The manager's job is not to tell people what to do but to create conditions in which competent people can do their best work. Anything else is waste.
Small is a strategy. Keeping divisions small preserves the feedback loops, accountability, and human connection that large organizations systematically destroy.
Walk around with genuine curiosity. Information that travels through formal reporting structures arrives filtered, summarized, and optimized for the comfort of the recipient. Go see for yourself.
Restraint concentrates resources. Every market you decline to enter, every acquisition you decline to make, frees capital and attention for the work that matters most.
Resilience is a moral quality. A company that can survive adversity without betraying its people or its principles is the only kind worth building.
Culture is architecture, not communication. Values exist not in what you say but in what you structure — in the financial model, the org chart, the compensation system, the physical space.
The founder's job is to make the founder unnecessary. Build systems so robust and so deeply encoded that the organization can thrive without you. Then test the hypothesis by stepping away.
