Looking for the old site?

How we collaborate to create products with integrity

by Ari Abraham

How we collaborate to create products with integrity

Apr 30, 2016

“If someone is able to show me that what I think or do is not right, I will happily change, for I seek the truth, by which no one was ever truly harmed. It is the person who continues in his self-deception and ignorance who is harmed.”
—Marcus Aurelius, Meditations

How do we seek truth and integrity in the process of building a product? It’s a curious question and perhaps not one we automatically think about. Regardless, it has been one I’ve been mulling since I began practicing product strategy here at Philosophie.

I start each day reminding myself that I know nothing. My understanding is often limited, hampered by a myriad of cognitive biases, as well as my own inherent flaws as a human being. In light of that I operate on the job in the spirit of collaboration, trying to figure out the best ways to be productive and useful to the developers and designers who I jam with.

Meanwhile, how are we as a company embracing this concept of a truthful product? It is perhaps testament to the thinking put into the work here that our mantra is make it better.

What is making it better if not about being open and prepared to:

  • as an individual, be fiercely transparent and receptive of all ideas from every member of the team
  • as a company to never accept a product as complete but rather as a continuous opportunity to test, learn, iterate and optimize

While certainly not definitive, the work we have accomplished to date at Philosophie certainly suggests that practicing the above makes for the most truthful product. We see that as being when minimum usable product meets the human problem we are trying to solve for.

What follows is an attempt to articulate some of the emergent learnings I have uncovered during my first twelve weeks here. I’ve spent a good portion of my time working with our enterprise clients thus a lot of the thinking contained in here relates to said experiences. They are certainly not things I practice with fluency yet. I myself am an iterative process in motion.

Let There Be Light

The organizational matrix of an enterprise company is a living, breathing, and complex system. It is easy to forget that it is made up of human beings. Human beings who are trying to both fulfill the needs of the system and their own personal goals.

More often than not there are a myriad of stakeholders, all invested in having different aspects of the product prioritized and they don’t always see eye to eye. It can be tricky to navigate this and strive to build a robust product that is hyper-focused on the user.

In such a situation, it is easy to fall back on process as a panacea. Just remember, process cannot trump people. Process cannot be wielded as a weapon against what we might deem as the inefficiencies of large organizations. There are no winners when we pit our process against their embedded ways of working. Channel your inner Yoda. Avoid being this person:

Providing our engineers and designers enough context of the inner workings of how the business, marketing and tech have to align in a large organization is vital to their work. This not only makes for better product development, it also helps bolster the consulting expertise of the wider team. We believe that all our Philosophers should be equal in their ability to empathize with a product owner be it entrepreneur or C-Suite.

Incept, Not Implement

We want our clients to be good at what they do. Manifesting that has never been through telling them how to do it. We show them through the work. This is to imbue them with the capability to continue building an ever better product when we step off the project.

But that’s not always an easy thing to do. Work is hard and change can be painful. Very often, when a product is being originated out of a large organization, the folks working on the project are typically:

  1. Drafted to participate on this new project. They perhaps have minimal to no experience with a digital product. It’s not their passion and they are not motivated by the work involved.
  2. Working to build something with limited freedom to operate and no real ownership over the product.
  3. Having to ramp up on methodology they have never encountered that we, the consultancy, are trying to get them to learn and use.

As product consultants we’re just amped to be building something new and can be blinded by this. We assume it’s fun for everyone but for the stakeholders involved, this is a pain in the ass and goddamn hard. So be kind. Err on the side of empathy always. It’s hard. I’m still guilty of the occasional curt email.

Experiment with the ways in which we introduce the process. Make it fun. Gamify it even. Never make it adversarial. Let them come round to it and in the meantime, just allow the work to be the vehicle for the process, not the other way around.

Learn Some Basic Programming

This is your common language. I say this because the one thing that binds the product is the code that manifests it. Code has no opinion, it has no shades of grey. It can be nothing but truthful.

Nobody expects me to deliver production code like my engineering brethren. However, being a product strategist with a working comprehension of programming makes for one who asks better questions and makes better choices for the product.

Making the effort to gain a surface understanding demonstrates commitment to our craft. I do it because I want to improve the quality of my work product. Growth in this role means becoming a teammate who is more holistic and armed with a deeper understanding of the work a balanced team is tasked with doing for a product owner.

“If someone is able to show me that what I think or do is not right, I will happily change…”

That is the crux of it I think. When I couple Aurelius’ words and what I have observed so far, my gut tells me that what us product peeps should aim for is:

  • Forging a path towards the most truthful version of the product that honors both the intention of the product owner and the need of the user
  • Being kind to each other and practicing our craft in the spirit of full transparency and cross-functionality
  • Always being mindful that the process is harder for the product owner than it is for us

My goal in the coming months is to embody these pillars as best as I humanly can. In doing so I hope to steer my team and clients to that truthful product they all work so hard at creating.

Https%3a%2f%2fimages.prismic.io%2fphilosophie website%2ff69930d6 f879 4567 a69a 7ac57a00287a https   cdn2.hubspot.net hubfs 2779272 ari photo.jpg%3fauto%3dcompress%2cformat?ixlib=rails 2.1

Ari Abraham is a Philosophie Product Strategist of American mind, Malaysian body, and British soul. Ari believes that good product is never in conflict with the betterment of humanity. Prior to Philosophie, Ari worked as an organizational designer with NOBL and Undercurrent. By night, he spends his hours honing his craft as a writer.

Get notified when we post new articles.