charlesroper.com

How I do it

I think about people first, not technology. I try to be caring and compassionate – with colleagues, users, and myself. I look at systems as a whole, not just the digital parts.

I make decisions based on what I know and what I learn. I work with others, share expertise, and solve problems together. I share work early and often – rough and unfinished – so I can get feedback and change course while it still matters.

I never stop learning. And I try to be open about what I am doing and why.

Think about people first

Technology should make life better. To do that, I start with people – not screens, not systems, not code.

• I talk to people and try to listen more than I speak.
• I try to test with real people regularly, not just at the end.
• I do research to understand who people are and what they actually need.

Be caring and compassionate

I work with digital technology, but I never forget: people are what matters.

• I try to think about how people use technology, not how technology uses people.
• I have patience with anyone who struggles with technology – and I try to understand why.
• I keep learning and growing, through training, reading, and reflection.
• I look out for the team.

Think about systems as a whole

Digital work does not happen in isolation. Every interaction sits inside a wider context – emotional, physical, and organisational.

• I try to start with "why", not "what" or "how".
• I ask what the person is actually trying to achieve.
• I consider how they might be thinking or feeling.
• I think about their physical needs and environment.
• I look at what happens before and after the digital part of the experience.

Make informed decisions

Good decisions need good evidence, but data alone is not enough. I balance hard evidence with expertise and gut instinct.

• I do research to understand users and their real needs.
• I talk to experts and non-experts, and listen to their feedback.
• I respect my own knowledge – and challenge it too.

Work with others

I am most useful when I get involved early, stay involved throughout, and help teams think more clearly about the problems they are solving.

• I try to get into projects early and stay engaged.
• I try to keep a strategic view, not just a task-level one.
• I challenge assumptions and offer a different perspective where it helps.
• I look ahead for new ideas, approaches, and technologies.
• I ask "why?" and "why not?"
• I try to be sensitive, understanding, and direct – as the situation calls for.

Share work early and often

Sharing work in progress – messy, unfinished, still being figured out – is more useful than sharing a polished final product that arrives too late to change.

• I share updates as the work happens, not just when it is done.
• Where I can, I show the thing itself: a prototype, a screenshot, a quick demo. It communicates more than a document about the thing.
• I try to work in short cycles towards big goals, getting feedback and revising as I go.
• I try to break projects into small pieces so value arrives early and often, rather than all at once at the end.
• I write updates that people can skim: a headline, a bit of context, and the detail for those who want it.

Never stop learning

I try to reflect on what has happened, learn from mistakes, and enjoy what went well.

• I look back at work done regularly, as well as forward at work to come.
• I try to do honest, blameless reviews at the end of projects.
• I try to be candid about where I can improve.
• I experiment and act on what I learn.

Make digital things anyone can use

Access to services matters. Not everyone needs the same experience, but everyone – regardless of their circumstances, abilities, or environment – should be able to get the service they need.

• I try to design with the core experience accessible to anyone.
• I try to understand and accommodate people's different abilities and contexts.

Be open about my work

Being open about what I am working on makes the work better. It sharpens thinking, invites collaboration, and builds trust over time.

• I write about what I am doing and what I have learned – and share it.
• I try to build a record of thinking over time: a blog, weeknotes, or a shared document – something I can look back on, and others can find.
• I talk to colleagues and users about the work. Often.
• I share early, rough versions of new work, not just the polished final thing.
• I contribute to open source and the wider community where I can.