Blog archive, page 4

Two white smartwatch mockups on a plain light background, one showing the face and one the back. The object is the whole picture, which is how a product page should open.

September 26, 2026Ecommerce

Product pages that explain the thing, then step aside

Lead a product page with the object, the price, and the one reason it exists. Materials, shipping, and the longer story come after a decision is possible.

By Hanabi

September 26, 2026Ecommerce

Ecommerce design for a brand, not a marketplace

A brand shop is an edited room with a point of view, not an infinite marketplace grid. Price, trust, and the path to pay still have to be obvious.

By Hanabi

Hands typing on a laptop at a wooden desk near a window. The desk is where you time the old chore and the new review.

September 26, 2026Automation

How to tell whether an automation saved time

Time the old chore against the minutes spent reviewing the automation. If checking it takes longer than the work did, remove it.

By Hanabi

A person in a purple shirt typing on a bright blue laptop at a round table. Support automation is still a reply someone has to be willing to send.

September 26, 2026Automation

Support automation that does not sound like a script

Support automation should use the brand's real sentences and offer a person when the question leaves the script. Do not give the bot an employee name.

By Hanabi

A person gesturing in a meeting, with a laptop showing a colorful layout, a notebook, and a phone on the table. The gesture is the judgment; the laptop is one set of options.

September 26, 2026Automation

How a studio can use AI in design without handing over judgment

A model can widen design options and speed production chores. The studio still decides what is clear, what is on brand, and what ships.

By Hanabi

A hand holding a stylus over a tablet covered in wireframe sketches, with a keyboard and mouse beside it. The sketches are the screen someone was already editing, which is where an assist belongs.

September 26, 2026Automation

Adding AI without turning the product into a chat box

Put an AI assist on the field the person was already editing. A blank chat is a new product they did not open the screen to learn.

By Hanabi

Hands sketching a user-flow diagram labeled user goals on a sheet of paper. The diagram is where a team draws the line between an automatic step and a human check.

September 26, 2026Automation

Where a human still has to review the work

Keep a person on anything a customer will see, pay, or be unable to undo. Draw that review into the workflow as a real control.

By Hanabi

A workshop where one person points at colorful sticky notes while others sit with laptops. The notes are the repeated handoff; the conversation is the judgment that stays human.

September 26, 2026Automation

When a service business should add automation

Automate the repeated handoff in a service business, such as scheduling and file delivery. Leave the judgment the client is paying for with a person.

By Hanabi

Two people pointing at a laptop screen, one wearing a fitness band. They are checking the same result, which is the posture a trustworthy feature should allow.

September 26, 2026Automation

Designing an AI feature people can trust

People trust an AI feature when they can see the source, the limit, and an easy edit. A confident wrong answer, with none of those, is a defect.

By Hanabi

A person in a purple shirt typing on a bright blue laptop at a round table. The picture sits with this piece because a community bot is still someone at a keyboard, answering in a shared room.

September 26, 2026Automation

Discord bots as a product surface

A Discord bot should live where the community already talks. Design a few commands, help text, and a real way to reach a person.

By Hanabi