Interface

how users interact with your ai solution and its visual design

This card covers how people will actually use your AI tool and what it looks like on screen. The interface shapes whether a journalist can fit the tool into a deadline workflow or sets it aside. A clear, simple surface matters more than a feature-rich one that confuses the people using it.

Questions to explore

// use these as prompts in a workshop or on your own. There are no right answers.

Where in a journalist's day does this tool appear, and what screen are they looking at when they reach for it?
What is the smallest set of buttons or fields a user needs to get a useful result?
How will the interface show when the AI is uncertain or working with thin information?
What existing tools does this need to sit beside, and how should it match or differ from them?
How will someone correct or undo what the AI produced without starting over?

Expert voices

// notes from the journalists and AI experts who helped shape this kit

“Tools might not be used if they are not easily accessible. Build AI into the CMS where journalists already work.”

Martin Schori, Aftonbladet

Things to consider

A plain, familiar layout usually beats a clever one for people working under deadline.
Show the user where the output came from so they can judge it, not just read it.
Test the interface with a real journalist before building more of it.

using this card

Pull Interface when it is relevant and set it aside when it is not. Pair it with the other AI Solutions cards, lay them out on a table, and use the questions above to get everyone on the same page. Capture what you discuss on sticky notes or in a shared doc.