To create a tech product that people remember, you have to go well beyond writing clean code. Alongside technical depth, you also need human understanding and ethical awareness. After years across different parts of tech, I weigh technological progress against human values. I don't have all the answers, but the teams behind every product that I admire put that balance at the core of their work.
I think about product development in terms of four pillars: value, empathy, trust, and ethics. Each one depends on the others, which means that a team that neglects any one of them weakens all four.
Value-driven products
The foundation of an outstanding product is the value that people get from it. In technology, a product's value consists of its functionality, its user experience, its security, and its ethical responsibility. Elegant code and efficient algorithms matter, but they matter because with them you solve problems that people face in the real world.
Figma is a strong example. In Figma, design teams have one shared platform for designing interfaces and sharing the work. Because designers and engineers work in the same space, each side sees the other's feedback sooner, so they improve the end product faster.
A tech product succeeds or fails on the value that real people get from it and on the problems that they can solve with it.
To build a value-driven product, start by understanding the specific needs and challenges of your target audience, which you learn through research and direct user feedback. That understanding, which comes from empathy, is how you make a product fit the people who use it.
How a product looks and how easy it is to use are also part of its value. With an attractive, intuitive interface, you can raise user satisfaction and loyalty, because people notice the care behind the design. Design thinking, which is the practice of weighing human needs, technological possibilities, and business success together, is how a team gets appearance and usability right.
Performance and scalability are equally important parts of that value. A product should keep working as its user base grows, especially in domains such as software engineering and financial technology, where customers lose money and confidence during every outage. For that reason, and fast response times are non-negotiable for keeping user trust.
Value principle
Build products for specific, well-understood problems. Technical excellence matters only when the people who use the product gain something tangible from it.
Design with empathy
Empathy is the foundation of meaningful product design. It means understanding users' needs, desires, and frustrations, then channelling that understanding into every decision that you make. Empathy sounds like a soft skill, but a team should use it at every stage of development.
Human-centred design in practice
In human-centred design, you put the user at the centre of every product decision. You watch how people use technology in their own environment, find their frustrations through direct conversation, and revise the product from what you learn. You may think that you know what users want, but the goal is to build what they need, which you confirm through their own words and behaviour.
The same approach applies to accessibility. Design for people with disabilities, for varying levels of technical literacy, and for different cultural contexts from the first sketch, because more people can then use your product.
AI and the empathy imperative
As AI and machine learning take on a larger role in products, empathy matters more. In a personalisation algorithm, a recommendation engine, or an automated decision system, a person can become a set of data points. A team that uses AI responsibly therefore puts the human experience first, so that its algorithms work for the people who use them.
Empathy principle
Design for the full spectrum of human experience. Learn about your users by watching them and talking to them, and build accessibility in from the first design.
The foundation of trust and security
A customer usually stays with a product that they trust, so security has to be part of product development from day one. Users entrust you with their data, which means that you have an ethical duty to safeguard it.
Be transparent about their data
Trust also depends on telling users plainly how you collect, store, use, and protect their data. A user who understands what happens to their information, and who feels respected in that exchange, has a reason to stay with your product. Write your privacy policy so that a customer without legal training can read it.
Security as a continuous practice
Security is continuous work, which means monitoring, regular audits, dependency updates, and a culture where every team member understands their role in protecting user data. When you do during the design phase, you find vulnerabilities before you release the code with those vulnerabilities in it.
Keep users' trust by being reliable
You build trust through consistency, because users need to know that your product will work when they need it, respond quickly under load, and recover from failures on its own. Reliability isn't glamorous, but with each reliable year you earn trust that a competitor would need the same number of years to match.
Trust principle
Protect user data, because your reputation depends on it. Be transparent about your practices, treat security as a continuous discipline, and earn trust through consistent reliability.
Ethical considerations
Ethical product development starts with a commitment to do no harm. In practice, you design a product with which you treat users fairly, compete on merit, and leave existing inequalities no wider.
Algorithmic fairness
In machine learning, your first responsibility is to make sure that the model's results are fair to every group of people. People collect training data from the world as it is, including its injustices, which is why you need regular audits, diverse testing datasets, and transparent methods to find bias and reduce it before anyone comes to harm.
Privacy as a right
Privacy is a right that product teams must defend at every stage of development. Data minimisation means collecting only the data that you need and keeping it only for as long as you need it. Make it your default, and give users clear, accessible control over their own information.
Broader societal impact
Through a product, a team can shape behaviour, sway opinion, and affect mental health. A product team that takes this influence seriously asks harder questions during design: Who could this harm? What happens if somebody misuses this feature? Are we amplifying voices that deserve amplification, or are we optimising for engagement at the expense of wellbeing?
Ethics principle
Hold your products to a higher standard than your customers ask for. Audit algorithms for bias, treat privacy as a non-negotiable right, and consider the broader societal impact of what you build.
Building with purpose
To build an outstanding tech product, you need all four pillars at once: value for the people who use it, empathy in its design, trust that you earn through security and reliability, and ethics in every decision. That means looking past revenue and market share to the lasting effect of our work on people and on society.
Our purpose as technologists is to meet today's needs with the products that we build, and through those products to leave the world fairer and healthier than it is today. From that point of view, every product that we build is a statement of our values, because the people who use it meet those values in each decision behind it.
