Matt Drozdzynski and the work of making work disappear

On a British Airways flight from Warsaw to London, Matt Drozdzynski was drinking coffee he considered dreadful and thinking about a remarkably productive weekend. He and his two co-founders, normally separated by miles, had spent two days in a hotel room examining their business. They talked, laughed, and worked through product and hiring plans for 2013. The coffee could be forgiven. The ideas were arriving faster than he could attend to them.

His company, then called Ink, had people working from homes and offices in half a dozen cities. Digital tools kept the work moving. Yet those two days together supplied something a video call had failed to provide: agreement about what deserved their attention. In his account, the difficulty of remote work was deciding what to work on. The internet had made communication convenient; shared purpose still required effort.

That scene is a useful place to meet the co-founder and CEO of Plane, the payroll and people platform formerly called Pilot. Drozdzynski now uses Matt Pelc publicly; his personal site has explicitly connected the two names. The companies and names have changed, but his writing keeps returning to a familiar irritation: how much machinery can accumulate around the apparently simple act of getting something done.

A founder of payroll software might be expected to enjoy administrative complexity. Matt seems considerably more interested in removing it. The hotel-room episode gives that ambition a human scale. There were people trying to build a business, separated by geography, discovering that having the tools was only the beginning. Someone still had to decide how the team would use them.

“It’s choosing what to work on that’s hard.”Matt Drozdzynski · Face time

A process borrowed in the wrong size

The early product team supplied another lesson. Matt had experience managing design and engineering for customers, but he described starting his own product team with very little experience of that particular job. He borrowed a process from Intercom, whose team was six times larger. It sounded sensible. Five months later, he wrote, the team was frustrated and the product remained unfinished.

He began again by listing what people actually needed: code reviews, clear explanations of features, an understanding of how much work could fit into a week. The resulting process was simpler. Feedback went into an Asana project, issues came up every two weeks, and proposed solutions became assigned tasks. He reported that the team took a product it had considered unshippable live in three months.

The embarrassment is part of the value of the story. A respectable process, adopted from a respected company, had still failed. His explanation was specific: creating a first product required different practices from developing an existing one. The team needed a system suited to its own work. An impressive diagram could not supply that understanding.

In a separate essay on management, he acknowledged another expensive assumption: that hiring good people would make management unnecessary. He credited Andy Grove’s High Output Management with changing his outlook. The admission gives his practical advice some weight. He had tried the appealing shortcut and discovered that capable colleagues still needed someone to help the organization function.

The meeting that stopped being a meeting

As Matt spent more time in the Bay Area, the team encountered a ten-hour time difference. Its daily standup call became a problem. The replacement was wonderfully unceremonious: a conversation in Asana where people recorded their progress, plans and obstacles at the start of their own working day. He reviewed the updates daily, responded and worked on blockers.

Then the team automated the start of that conversation. Zapier sent an email into Asana at 8 a.m. UTC. The reminder no longer depended on a colleague remembering to post it. Matt explained that searchable updates were a reason for choosing this arrangement over Slack. A small routine had become asynchronous, repeatable and easier to look back through.

Here was a distributed company adjusting an ordinary management habit to the lives of the people doing the work. A daily call had offered one moment of synchronization. Written updates offered different moments, with a record attached. The relevant question was whether the team could keep track of its work, rather than whether everyone could perform the familiar ritual together.

His essay on a “Minimum Viable Process” develops the same idea more broadly. Observe how work happens before redesigning it. Start small, define the outcome, then make incremental changes. Treat adoption as part of the job. A procedure people cannot or will not use has a rather limited claim to success, however handsomely it has been documented.

Pilot finds the recurring problem

By 2017, Pilot had joined Y Combinator’s Winter batch. Today, YC describes Plane as a platform for fast-growing teams managing global payroll and compliance. Between those descriptions sits an evolution from finding talent to handling the work that follows a hire. Matt’s early distributed-team experience made that later problem familiar territory.

The transition has a concrete place in his public conversations. In August 2020, he joined Peer Richelsen on The Lean Hire Podcast to discuss being a European entrepreneur in Silicon Valley and hiring internationally. That same month, he spoke with Sondre Rasch on Building Remotely about the systems and mistakes involved in employing people across borders.

He also appeared in a June 2020 remote-worker compliance webinar. Its agenda included getting paid, tax forms and the logistics of working for an employer in another country. These are the questions that follow the celebratory announcement of a global hire. The announcement is brief; the arrangement has to keep working on every subsequent payday.

In May 2023, Pilot became Plane. The company’s announcement explained the practical continuity: existing pages would redirect, contracts and payments would continue, and Pilot Platform Inc. remained the legal entity. A launch event with Matt, Head of People Irene Chao and Head of Product Rob Lee introduced the expanded people platform. Even a new name arrived accompanied by instructions about what happened to the old paperwork.

The person comes before the contract

In 2023, Matt described a product choice that reveals his priorities. When adding somebody to Plane, the user began with the person; the employment arrangement followed. His ambition was to bring different kinds of workers into a common payroll experience, while handling their distinct requirements behind it. The interface began where a hiring manager’s attention already was.

He applied a similarly direct test to payments. The money should reach the worker’s nominated bank account on time. A balance inside a wallet did not, in his view, complete the job if withdrawing it introduced another delay or fee. That was a principle he articulated in an interview, rather than a reason to assume every payment would always proceed perfectly.

The distinction matters because payroll is unusually personal software. To the administrator it is a recurring task; to the recipient it is earned money. A successful interaction may leave very little to admire on screen. Matt’s interest in removing steps makes sense here. The more ordinary the arrival of the money feels, the less of the system the worker has to think about.

His public discussions continue to examine the costs around that experience. In a 2025 panel, he joined Workweek’s Hebba Youssef and Barstool Sports’ Rachel Ackerman to discuss international contractor payroll, currency markups and vendor contracts. The conversation approached payroll through its bill as well as its interface. A tidy subscription price can coexist with expenses that deserve a closer look.

A digital pack rat with a delete key

Matt describes himself as a digital pack rat. He records ideas, tasks and notes, but also enjoys deleting things: half-started projects, old intentions, the clutter that gathers in a task manager. An overflowing list can become its own obstacle. Clearing it creates room to choose again. There is a modest comic pleasure in a software founder finding liberation in the delete key.

Notes receive different treatment. He values a searchable archive and has written about using a computer to explore more than a decade of his ideas. He sees the possibility of asking questions of past thinking, finding themes and revisiting earlier dreams. Saving thoughts and discarding obligations can coexist. One preserves material for reflection; the other prevents yesterday’s intentions from monopolizing tomorrow.

Writing has required its own simplification. In an essay he says he drafted by hand in the summer of 2011, he describes getting stuck choosing publishing tools. Writing had become entangled with editing, platforms and an imagined audience. Taking publication out of the task allowed him to express a thought. The paper and pen accomplished what the search for an ideal application had postponed.

His short essay “Full stack” recommends learning enough design, code, marketing, sales and business fundamentals to get something into people’s hands. It is advice about practical range. A founder who can carry an idea through several stages can begin without assembling a committee for every step. That preference fits the builder who keeps looking for a smaller workable process.

What is worth keeping?

His reading recommendations connect careful expression with company-building. Fellow founder Weiting Liu has described conversations with him and highlighted two books Matt recommends: The Pyramid Principle and Several Short Sentences About Writing. Both recommendations sit comfortably beside his own compact essays. A clear sentence asks the writer to decide what matters before asking the reader to care.

His technical interests have also had a public life. His personal site lists a 2011 EuRuKo talk on machine learning and sentiment classification in Ruby, later talks about productivity and Slack bots, and more recent payroll panels. The subjects change, but the range helps explain why an organizational problem might send him toward a technical experiment rather than another standing appointment.

The aspiration behind Plane is broad: make starting and running a global business easier. Its current work includes automation and ways for AI tools to interact with payroll and HR data. That development fits a long-running concern in Matt’s writing about how much routine work a system can absorb. It also raises the familiar management question of what people still need to judge for themselves.

The hotel-room weekend remains a useful counterweight to the software ambition. In that early account, colleagues needed time together to agree on their direction. A routine could be automated; a purpose had to be discussed. Matt’s career offers a series of attempts to distinguish the two. The result he keeps working toward is a business in which the machinery takes less attention, leaving people more room to decide what deserves it.