Nathaniel Whittemore

Model agnostic and works from Slack or Telegram.

Try it at zenflow.free.

Teams of any size and technical depth can use OutSystems to build, deploy, and manage AI apps and agents quickly and cost-effectively without compromising reliability and security.

With OutSystems, you can rapidly launch ideas from concept to completion.

It's the leading agentic systems platform that is unified, agile, and enterprise-proven, allowing you to accelerate growth, reduce operational friction, and deliver real enterprise impact with AI.

OutSystems.

Build your agentic future.

Okay, so we've talked through about a dozen or more problems with traditional knowledge work artifacts that websites can solve, but what are some of the best examples that you as a knowledge worker could actually go out and try?

I've got 18 different examples here, so we'll go through them pretty quickly, but I do want you to watch out for some common patterns.

One pattern is about distribution.

A lot of these things are the types of things that get forwarded around a committee without you in the room.

Another pattern is things that keep evolving after you quote-unquote finish them.

A third pattern is things that scatter across different channels.

The goal in sharing these is not that you're going to use all of these examples, but instead that if these types of artifacts are things that you regularly interact with or create in the course of your work, they're worth considering whether building a website might be, in some cases, a better alternative.

The first and perhaps most obvious one is exactly what I'm doing now, building a narrative website instead of a traditional slide deck.

Now, if you've used any of the AI native presentation tools like Gamma, you'll know that they're already collapsing the space between a slide deck and a website.

And I think that that's a mega trend that's just going to continue.

Also, directionally, a lot of the SaaS tools that are used to distribute PDFs are just approximating with features the things that websites can do natively, including updating them to the latest version and doing access provisioning.

But what those tools don't have that native websites do is a lot of the other stuff we just talked about, like the ability to build interactive features or the ability to break out of the 16 by 9 aspect ratio, the ability to easily link things out and connect your presentation to other parts of the context.

If you do nothing else in this, I would very much suggest starting to explore whether on average and by default, the slide decks that you build currently should just become narrative websites instead.