Human Should Decide Button
A one-button website that records a single human action.
Start new thread
Rania ZYANE

Human Should Decide Button - A one-button website that records a single human action.

by•
Only press if you believe a human should decide. Most products optimize for engagement, efficiency, or outcomes. This one doesn’t. It consists of a single button whose only function is to record that a human chose to press it. There are no accounts, rewards, or actions beyond that. A short daily observation is shown to reflect how the button is being used. This project exists to prove that a single human action still matters, even when it does nothing.

Add a comment

Replies

Best
Rania ZYANE
Maker
📌
Hi, I’m the maker. I built this because most things online are designed to extract attention, optimize behavior, or push toward an outcome. I wanted to build something that didn’t do any of that : something that asked for a single action and nothing more. The “problem,” if there was one, wasn’t technical. It was the feeling that even very small interactions online are usually framed as data to be optimized or monetized. I was curious what would happen if an interaction was recorded but not used for anything. The process stayed intentionally constrained. I kept removing features instead of adding them, and any idea that introduced rewards, personalization, monetization, or goals was dropped. The only thing that evolved was the daily observation, which emerged as a way to acknowledge that the system is noticing people without asking anything from them. I’m here all day and genuinely curious how others interpret this. There’s no right way to use it.
Nika

I would wish there should be an edit button for a created text (I messed up my English grammar) :D

Rania ZYANE
Maker

Thank you @busmark_w_nika for this feedback. Although the "context" is fully anonymos. Do you think the "edit" would be relevant ?

Nika

@raniazyane If I mistyped, it would be useful :)

Rania ZYANE
Maker

@busmark_w_nika I appreciate the insight and will incorporate it.

Christopher Kilpatrick
I’m a little confused on how to use this. Is the goal to provide an anonymous public record where we can all see real examples of ways automated systems are impacting people where having a human in the loop would’ve made it better? So, I don’t press the button now, but if I encounter an AI customer service agent a week from now that can’t solve my problem, then I would come back to your site and press the button so there’s a record of that problem occurring? 
Rania ZYANE
Maker

@kilpatrick Great question. yes, that’s the idea.

It’s not a complaint platform or escalation channel. It’s a public, anonymous signal.

If you experience a situation where you believe a human should have made the decision, you can record that moment by pressing the button.

The goal is to surface patterns around where people feel human judgment still matters.

Christopher Kilpatrick
@raniazyane Ok, that’s cool! Seems like you are basically doing for non-optimal  automated processes what DownDetector does for poorly functioning  websites/apps. If enough people use this, that could form an interesting dataset for people to see aggregate  impacts of automated decisions/feedback. Do you have any plans to tie button presses to specific companies or processes the way DownDetector does? 
Rania ZYANE
Maker

@kilpatrick That’s a thoughtful comparison and yes, aggregation is definitely part of the vision.

Users can already select a category when they press the button (money, health, work, etc.), which allows patterns to emerge across domains.

There’s also a public read-only API that aggregates presses over time so anyone can analyze trends (by category, timestamp, frequency) without accessing personal data. The idea is to make the signal observable and measurable while keeping it anonymous and non-targeted.

For now, I’m intentionally avoiding company-level tagging. I want this to remain a calm indicator of where people feel human judgment matters not a "complaints directory".

If adoption grows, there could be more structured aggregation around process types but always without turning it into a name-and-shame platform.

Rania ZYANE
Maker

Hello,

One thing I want to clarify: this isn’t meant to be anti-automation.

I use automated systems every day, and most of the time they work well. This is more about the edge cases. The moments where a decision feels final and there’s no visible path back to human judgment.

The button doesn’t solve that. It just records that someone felt that boundary.