Respect different paths
Consider the contribution someone can make and the context behind their experience. Explain expectations in clear language and make room for questions rather than relying on unspoken codes.
Life at ORIGO
A culture built through everyday choices.
Feeling respected, understanding why your work matters and being able to keep learning: the foundations of the working environment we want to build.
People first
Room to contribute. Space to be yourself.
A healthy working relationship starts with attention to people. Listening, reliable communication and consideration for different backgrounds shape how we want to work with future colleagues and contributors.
We want people to understand the purpose of a task, have access to the context they need and be comfortable asking a difficult question. Respect should be visible in the way an idea is discussed, a concern is handled and a commitment is made.
These are the working principles we intend to put into practice as the studio grows. Working arrangements, support and development opportunities will be defined for the actual collaboration rather than assumed from a general promise.
Belong through participation
Different experiences make the work stronger.
Belonging begins with concrete behaviours: who is heard, how information circulates and how we respond when someone needs help.
Share the context
Make product decisions and practical constraints understandable. Write down information that others will need, including people who were not present in the first discussion.
Raise concerns with care
Address disagreements through facts and specific examples. Ask what is needed to move forward and make escalation possible when a concern cannot be resolved in the immediate conversation.
A useful rhythm
Focus, connect, learn.
We want a rhythm that supports considered work and makes progress visible, with practical expectations agreed for each contribution.
Protect focused work
Set a clear priority and a realistic next step. Use meetings for decisions and collaboration, and written context for information that people can absorb in their own time.
Connect across domains
Bring technical and professional perspectives together around an actual workflow. A teacher, a practitioner or a partner can reveal a need that a feature list alone does not explain.
Leave a learning trail
Document a decision, an experiment and its outcome. Make what you discover reusable, so that the next person can start with understanding rather than reconstructing the whole story.
How our values become actions
The way we want to work together.
Teamwork
Share context early, ask for help when it matters and make knowledge available to others. A product moves forward when design, technology, domain knowledge and customer understanding inform the same decision.
Integrity
Say what a product can do today, honour the commitments we make and raise concerns openly. Respect for people, their information and the work they entrust to us belongs in everyday decisions.
Humility
Treat expertise as something to share and assumptions as something to test. A question from a colleague or a user can reveal an issue that a polished presentation has missed.
Passion
Care about the problem as well as the craft. Let curiosity improve the experience, and let useful feedback turn energy into focused work that people can understand and use.
Accountability
Make the owner, next action and review point clear. When a commitment becomes difficult to meet, explain it early, propose an adjustment and follow through on the decision.
Useful results
Look for changes in the user’s actual workflow: less uncertainty, an easier step or a better-informed choice. Review what happened and use the evidence to choose what deserves attention next.
Continue the conversation
What would you bring to the conversation?
Share your interests, skills and a concrete example of work that matters to you.