I was on a screen share, helping someone with Notion, when I realized I had stopped looking at the page and started looking at their work.

The database design mattered. The properties mattered too. But the real friction was somewhere else.

Who was actually making decisions?
Where did those decisions live?
Why did the workflow already feel vague before the tool even entered the picture?

That happens to me a lot with Notion.

You think you are talking about software, and then suddenly you are talking about judgment, coordination, and the shape of work itself.

That is where Weekly Noticon starts.

I’m Shikata, a Notion Certified Consultant.

This is not a newsletter that teaches Notion in order.

It is closer to an entertainment magazine built around experiments.

I use Notion as a device for testing the strange realities of work, information, team operations, and sometimes AI. The point is not just to explain the tool. The point is to see what the tool reveals when you actually try to use it seriously.

The format is usually this:

A silly starting point
→ Serious testing
→ Something useful left behind

The starting point can be a little dumb.

“Does a dashboard go stale in two days?”
“Is your read-later list just a graveyard?”
“Are you organizing things, or only getting the feeling that you are?”

But I do not want to leave it at a joke.

I want to count, compare, reproduce, and test until something real shows up.

In the first issue, I built eight AI rappers inside Notion and made them battle in a tournament.

Each match cost 115 yen.

Yes, it was stupid.

But that kind of stupid is useful. When you use a product in a weird way, its quirks often show up faster than they do in the “correct” use case. Push the system a little, and it tells on itself.

That is the kind of thing I want to notice, test, and write about.

I do not want to leave you with a neat summary. I want to leave you with judgment.

Maybe something like:

“This part is a bad idea.”
“This change might actually help.”
“This looks efficient, but it is probably a trap.”

And if possible, I want to leave something tangible too. A checklist. A mini template. A lightweight rule you can take back to your own work.

The free version will always be written to stand on its own. I do not want to cut the piece in half and treat the ending like a paywall.

There is, however, another room beyond the main piece.

That room is for the heavier material: full experiment logs, failure notes, comparison tables, templates, operating recipes,
and prompts.

Not a continuation, exactly. More like an extra room for people who want the deeper layer.

And then there is the after-school part: Discord.

The newsletter is for reading. Discord is for talking. It is where the follow-up questions go. The edge cases. The “what would this look like in my team?” conversations.

The main thing is still the newsletter. Discord is just for people who want to stay in the conversation a little longer.

This newsletter is obviously for people who already like Notion.

But Notion is not always the real subject.

A lot of the time, the real subject is blocked work, messy information, awkward team processes, or the gap between how people say they use AI and how they actually use it.

So even if you are not deeply into Notion, you may still find something useful here.

If this sounds like your kind of thing, start with the free subscription.

Every week, I will begin with something slightly ridiculous, take it seriously, and leave something behind.