Jessica Ko Is Making the Folder Give Up Its Secrets

Jessica Ko's company began with a file that ought to have been easy to find. At Opendoor, where she led design as the company expanded, requests arrived from across the business: the white logo, a particular photograph, one more marketing asset required five minutes ago. The design team opened Dropbox and Google Drive, descended through nested folders, and searched. Hours went missing. Occasionally an image stayed so thoroughly lost that somebody recreated it or bought it again. The asset existed. Practically speaking, it did not.

There are startup origin stories involving scientific breakthroughs and dramatic encounters with fate. Playbook's is funnier because it is painfully ordinary. Ko noticed that creative people, hired for judgment and invention, were moonlighting as disappointed archivists. The computer could store the work but could not understand much about it. A folder knew where an image had been put. It knew nothing of the red chair in the image, the campaign it belonged to, or the colleague who needed to approve it.

Ko had spent years close enough to the problem to distrust cosmetic fixes. She designed products and recruited designers at Google, worked with YouTube, and became Opendoor's founding designer and later Head of Design. She also worked at Humu. Those roles taught her how quickly a tidy system becomes untidy when a company grows, and how often creative operations are treated as an afterthought to creativity itself.

A filing cabinet built for pictures

Ko and designer-engineer Alex Zirbel co-founded Playbook in San Francisco in 2019. The early pitch was direct: creative work deserved a home that looked and behaved like creative work. Instead of forcing a photographer, brand team, game artist, or agency into a gray hierarchy of filenames, Playbook displayed assets on visual boards, added tags, grouped versions, and made sharing feel closer to presenting than attaching.

The distinction sounds small until one considers what a creative file carries. A photograph contains a subject, a mood, a palette, a license, a client decision, and perhaps six prior versions that should never again be mistaken for final-final-3. Ko's product thesis was that media storage should preserve more of that meaning. Search could use image contents, extracted text, color, and similarity. Collaboration could stay beside the asset. The cabinet might finally learn what was in its own drawers.

“I think a monetization strategy can be as innovative as a product.”Jessica Ko, on building Playbook's business model

That sentence explains a less visible piece of Ko's design practice. Other cloud-storage companies charged for capacity. She did not want Playbook's future chained to selling more digital shelf space, so the company offered generous storage to creatives and reserved paid value for the work that could happen after files were organized. Pricing, in her telling, establishes a direction. Charge for the warehouse and you will keep improving the warehouse. Charge for useful motion and the product has permission to move.

The distribution followed the same logic. Early adopters received the pro tier free while the team refined the product and its community rules. Playbook worked with established design communities including Dribbble and Creative Market, running workshops and publishing practical guidance where designers already gathered. The product's visual links carried the product with them. A shared board was also a small demonstration.

The day after the seed round

Building the first team supplied a brutal timing joke. Playbook closed its seed financing. One day later, COVID-19 lockdowns began. Meeting potential colleagues became difficult, and persuading people to leave stable jobs for a new company became harder still. Ko and Zirbel had an unusual advantage: both could design and engineer. They put their heads down and continued building while the social machinery of startup recruiting sat idle.

The first employees arrived months later. Ko remembered the delay without romanticizing it, but the constraint sharpened an operating belief: makers should be able to keep making. Her 2020 recruiting note advertised “less cult building, more product building,” encouraged experiments and unusual working routines, and promised room for people to try roles beyond the one on their job description. Its tone was more workshop than cathedral.

She was equally plain about recruiting. Great employees bring other great employees when they are treated well. Engineering talent could also be attracted by the material itself. Images, video, art, and design posed interesting technical questions, and the beauty of the source material made code and architecture feel less abstract. A visual product gave engineers something lovely to look at while solving difficult retrieval problems. Not every database can offer that courtesy.

Craft needs an audience

Ko's interest in making work legible extends beyond software. She helped establish Design Collective, a volunteer community that paired aspiring UX designers with experienced mentors. Participants chose a real design problem, met mentors weekly, joined group critiques, and emerged with a published case study. It addressed another kind of buried asset: skill that a junior designer possessed but could not yet present clearly enough to be hired.

Her portfolio advice carried the bluntness of someone who had reviewed many. Craft matters, but so does evidence that a candidate cares about the employer's specific problem. A large company, startup, and agency are not interchangeable audiences. The portfolio should be relevant, show range, tell a coherent story, and make the candidate's judgment visible. A generic tour of screens asks the reviewer to do the organizing. Ko prefers the designer to do it.

She has lived the managerial version of that lesson too. In her own essays, Ko wrote about becoming Head of Design after joining a startup as its first designer, and about the awkward leap from making work to managing the people who make it. The promotion can look like a reward while quietly replacing the craft that earned it. Her writing treats management as another design problem: expectations need structure, feedback needs care, and a growing team needs more than the habits that worked when ten people could settle a question by turning their chairs. The observation helps explain why Playbook gives review, comments, versions, and role controls a place beside the files. Collaboration is not a meeting layered onto the work. It leaves a trail inside the work.

That principle loops neatly back to Playbook. A portfolio organizes creative judgment for a hiring manager. A visual library organizes a team's judgment for colleagues and clients. Both are acts of retrieval and presentation. Both collapse when context goes missing. Ko has spent much of her career making context harder to lose.

“I care about their craft. But I also care just as much, if not more, about how much that person cares about my problem.”Jessica Ko, on reviewing design portfolios

AI gets the chores

In April 2026, Ko introduced Playbook Intelligence with a useful boundary. She rejected the idea of replacing human creativity with AI. Her target was the dumb work that burns creators out: assembling all files for a client, cleaning an intake folder, cropping a batch of images, removing backgrounds, applying a watermark. The new interface let teams describe those jobs in ordinary language. If the platform understood the request, it could find the material and perform the operation.

By then, Ko said Playbook supported more than 5,000 teams with at least ten members and more than 500 with at least fifty. The company's site reports 2.5 million registered users and more than 450 million assets. Scale changed the folder problem without changing its nature. A lone freelancer may misplace a draft. A global brand may lose the approved campaign inside a small civilization of almost-identical versions. The anxiety compounds faster than the storage bill.

Playbook Intelligence brings Ko's original observation to its logical next step. Seeing every file is useful. Finding the right one is better. Acting on it without opening six menus is where storage becomes workflow. The system moves from shelf to assistant, while the person retains the part that demands taste, intent, and responsibility.

Ko's public writing has always been unusually willing to admit boredom, bad culture, managerial uncertainty, and the indignity of hunting for files. That candor is more than voice. It is a method of product discovery. Irritation becomes data once someone stops pretending it is beneath notice.

The folder survived for decades because everyone understood it. Its weakness was exactly the same: everyone understood its limits so well that they stopped expecting more. Ko expected more. She saw the white-logo request, the duplicate purchase, and the wilting asset in a far-off directory, then decided the filing cabinet had enjoyed a long enough retirement inside the computer.