← All work
The reference my bookmarks were trying to be
Noir Book, a self-initiated Product Office project, 2026
Noir Book, a self-initiated Product Office project, 2026
My role: the whole thing, end to end. I chose the problem, defined the structure, curated and distilled the content, designed the system, and shipped it myself.
Good frameworks were saved across scattered bookmarks, notes from courses faded after a month, useful things sat somewhere I could not quickly find again. Not always lost, but it usually took far too long to get back to the thing I needed.
I also wanted one place that covered the disciplines together, UX, product, marketing, and content, instead of a different site for each. On real work they overlap constantly, so it helps to see them side by side. And I wanted every topic in one format I already know, so finding what I need is quick.
Noir Book grew into a fairly big library. 127 topics across the four disciplines, each with the idea, a method with a template, and a real example. You arrive with a problem, search, find the framework, and use it in a couple of minutes. No signup, no lessons to unlock.
Frameworks and methods, each with a template you can lift straight into a project.
Roughly 25 hours of reading if you ever went front to back, which is the opposite of the point.
UX, product, marketing, and content, in one format so they can be cross-examined side by side.
A machine-readable layer lets an AI assistant pull the right topic straight into your workflow.
The library below is the real, working product. Search it, toggle a discipline, filter by depth, open a topic. It runs on a design system I built myself, with light and dark mode.
Every topic follows the same three-part structure, the idea, a method with a template, and a worked example, so once you know one page, you know them all. That consistency is the point: it is what turns scattered reading into something you can use mid-project.
I started from the frameworks I already used in product and UX, listed them out, then settled on one page structure for every topic: the core idea, a practical method with a template, and a real example. Writing each page meant pulling from the strongest sources and distilling them into that same tight format, cutting the padding so what is left is usable mid-project. Most of the work was that editing and structuring, turning scattered, long-winded material into one consistent, findable shape.
For UX especially, there are courses that go deeper on the theory, and that is fine. But on a live project you often need the practical version more than the deep one, and that gap is where this library comes from.
Later I added topics people asked for, some outside my own day-to-day experience. Since that knowledge is well established and public, the job there was the same as everywhere else: read the good sources, fit them to the structure, make them usable. The person who requested each one told me whether it actually helped.
Honestly, it was a lot of fun to build, and it turned out genuinely useful. The best sign was that people I shared it with kept coming back with "oh nice, can you add this too?" That kept it growing, and it is how a good share of the topics got added.
It is a straightforward example of how I like to work: notice a real, everyday problem, decide what would actually fix it, and build the whole thing, rather than stopping at a plan or a mockup. Not a deck, not a concept, a working tool people use on real projects.