Docs.com

Docs.com let anyone publish a Word doc, a PowerPoint, a Sway, or a PDF straight to the open web — in full Office fidelity, free, with a link anyone could open. I designed how all of it worked — from the file on your laptop to a page with your name on it.

Docs.com was a social network for documents. People could publish, discover, view, download, and share Office files in full high fidelity — Word, Excel, PowerPoint, Mix videos, Sways, images, PDFs, even web links — from a profile page that was theirs. They could follow other authors, form groups and organizations, and decide for each document exactly how open it was: read-only, or free to copy, download, and reuse.

The point was high fidelity. Microsoft wanted to show that every Office product now lived on the web — that a document you made in Office could be showcased online looking exactly as you built it, even if you weren’t editing it there. And Microsoft had no social network of its own at the time, so Docs.com became the professional sharing hub Office didn’t have — a place for professionals, writers, and amateurs to publish their work, share it, and let others build on it. (SlideShare let you post a PowerPoint, but not in high fidelity, and you couldn’t download it and make it your own. Docs.com was about creation, control, and rights — not just posting a file.)

The scope was enormous, and the whole Tokyo team ran at it in weekly sprints. I led the design: the publish flow, the profile, the way people found each other’s work, and the content tile everything else hung off of.

Underneath every use of Docs.com was the same wish: get a document out into the world — looking right, findable, and without the overhead of a website. It showed up in a lot of forms:

She teaches from a OneNote notebook she’s spent years building, and she wants more than for students to see it — she wants them to take it, work in it, and build on each other’s work out in the open. For her, amazing is a living resource the whole class can take, add to, and learn from together — free, no login wall, no LMS in the way — the kind of thing that lifts every student, and her along with them.

This is Dana’s journey, start to finish — from fighting the login wall on everything she shared, to the day her students were building on each other’s work in the open and teachers from grade school to university were copying her lesson into their own classrooms.

Paul is an independent consultant with sharp decks and reports and no website to put them on. He doesn’t want to become a webmaster — he wants his work online, looking exactly as he built it, and found by the right people. For him, amazing is a discoverable, branded showroom with no website to run.

Paul’s journey turns on a different question than Dana’s. Not “can they take it” but will this look like my work, and will the right people ever find it?

Zoe just finished a degree and a pile of good projects, and she’s applying for jobs with a résumé and nothing to point to. She doesn’t need a whole website — she needs one clean, credible place that’s hers. For her, amazing is a public home for her work, at her own name, in minutes.

Zoe’s journey is the shortest and the most personal. It turns on one question: can I make this feel like a real place that’s mine — before the application closes?

Set the software aside for a second. The perfect version of Docs.com is that your work is just out there — looking exactly as you made it, found by the right people, and completely under your control. You never wonder if it broke on the way up, or who can see it, or whether it’s really yours.

The wall was never the upload. Uploading a file is easy. The hard part is the nerve it takes to put your work on the open web at all — the worry that it’ll look wrong, that the wrong people will see it, that it won’t feel like yours. So the real problem wasn’t “make uploading simpler.” It was to close the gap between that fearless ideal and how exposed publishing actually feels — and the only thing that closes it is trust. Full fidelity so it looks right. Visibility you control so you decide who sees it. A profile that feels like home so it’s unmistakably yours.

This was the call I pushed hardest for. The pressure on a product like this is always toward reach — get more documents up, get more of them seen. But I kept coming back to a different instinct: people don’t publish what they can’t control. Trust, not traffic, is what makes someone put their real work on the open web.

So control was never a buried setting. Every author decided, in plain language at the moment of publishing, exactly who could see a document — just them, a group or organization, or the whole world — and exactly what others could do with it: view only, or copy, download, and reuse. That’s the difference between someone who tries it once and someone who comes back to publish again.

This is the belief I hold most stubbornly, and it didn’t come from a book. Everything I know about trust and security in a product, I learned by watching what happens when they get treated as someone else’s job. On Docs.com I argued — hard — that control has to come before scale: that a product isn’t ready to grow until people can trust what happens to what they publish. That conviction is why control sits at the center of everything here.

Everything on Docs.com was a tile — a document reduced to one image, a title, and an author. It’s what made a wall of mixed Word docs, decks, notebooks, and PDFs read as one coherent library instead of a junk drawer. I designed the tile to do two jobs at once: give the author a piece of their own brand — a background image they chose — and give the viewer an instant, honest signal about what a document was before they clicked. Microsoft patented the design.

The hub was the front door — the page that had to turn someone who’d landed on Docs.com into someone who actually published a document. That first-time author step was the hardest number in the whole product to move, so we didn’t argue about the pitch in a conference room. We tested it.

One thing the chart doesn’t show: the single highest-converting variant was also the most generic — and shipping it would have meant stripping the character out of the page. So we shipped the one just behind it. A test tells you what converts; it doesn’t tell you what’s worth shipping.

Publish twice and you earned a vanity URL — docs.com/yourname — and the profile behind it became a real home: a journal, your documents, collections you curated, an About page that read like a portfolio. This is where “I posted a file” turned into “this is my place on the web,” so we researched it with real people — lightweight MVPs in front of users, and visits to schools to watch teachers actually publish and share.

Docs.com was a real Office product, but Office was still inventing its cross-product, web-based design language while I was designing it. The system was in constant flux — page styles and elements kept shifting underneath me — and it is very hard to design a real Office product without a real Office design system to build on. Keeping Docs coherent while the ground moved was the actual job.

The ground moved organizationally too. On Docs.com I moved out of Microsoft’s user-research organization and into the Office design organization in Redmond — the group behind the original Docs framework — under a new design manager. New reporting line, new manager, and a design system being invented in real time.

What kept it honest was evidence over opinion. I built multiple UX and UI flows from the previous team’s research, then A/B flight-tested competing designs and ran user interviews to lift acquisition, engagement, and usability — so what shipped was what the research backed.

The work wasn’t settled in decks. The publish flow and the hub variants were mocked, put in front of users, and revised on what people actually did — not what we hoped they’d do. The upload flow below is the kind of thing we worked screen by screen, because the moment of publishing is the moment the whole product either earns trust or loses it.

Boil the whole product down and it’s six steps. The fourth one, choosing who sees it, is the one that earns the trust.

Published documents landed as tiles on your profile and across the site — full Office fidelity, one link, findable by search. A mix of decks, reports, notebooks, and PDFs from thousands of authors read as one coherent library, because the tile did its job.

All three journeys end the same way — somebody telling everyone they know. But that’s not the finish line. It’s the feedback that writes the next brief. Watching how people actually used Docs.com — teachers handing out notebooks, consultants building showrooms, graduates turning the profile into a personal home — came right back and shaped what we built next.

Docs.com relaunched in 2015 as Microsoft’s real attempt to make the open web a first-class place for an Office document — full fidelity, free, and yours. It grew fast: 12% a month, and 70 million people in its first year. What I designed — the publish flow, the profile, the way people followed and shared, and the patented content tile — proved the idea that your work deserves a home on the web that looks exactly as you made it.