Skip to content
Values
Our main values are User Centric, Default to action, Growth, Collaboration, Trust, Transparency, Iteration & Feedback.
©️ User Centric
We obsessively think about our user's digital and professional requirements and translate that into our product.
By putting our users at the center of everything we do, we can build products that truly meet their needs and exceed their expectations.
For us, being User Centric means starting every decision with the question, "How will this benefit our users?" We strive to understand our users' needs, preferences, and pain points, and to use that knowledge to inform every aspect of our product development process.
We take a data-driven approach to understanding our users, using tools like user surveys, feedback forms, and analytics to gather insights that help us make informed decisions about product features, design, and functionality. We also prioritize user testing and feedback, gathering input from users at every stage of the development process to ensure that our product is meeting their needs and delivering value.
Being User Centric is not just about building great products, however. It's also about fostering a culture of empathy and understanding within our company. We believe that by truly caring about our users, we can create a culture of innovation, collaboration, and excellence that benefits everyone.
Tips on how to apply being User Centric
Example (do this…)
vs. Counter-example (...not this)
I prioritize features and functionality based on their value to users, rather than solely on technical feasibility or internal goals.
I prioritize features based on what's easiest to build, or what will make the company the most money, without considering user needs.
I design products with usability in mind, making them intuitive and easy to navigate.
I design products that prioritize aesthetics over usability, or that require extensive training or support to use.
I seek feedback from users throughout the development process, and use that feedback to iterate and improve the product.
I wait until the product is fully developed to seek user feedback, or ignore user feedback in favor of internal opinions.
I advocate for the needs of users within the organization, and work to ensure that all team members understand the importance of user-centricity.
I prioritize internal goals or politics over user needs, or dismiss user feedback as unimportant or irrelevant.
There are no rows in this table
🏄 Default to action
(shamelessly taken from zapier, because if it’s there and it’s good why not :), see )
Delivering something real today—and learning from it—is typically better than delivering something of questionably better quality next week.
However: action is not an achievement unto itself. Instead, our actions should connect to clear priorities and outcomes, especially what's best for our mission and customers.
Tips on how to apply (and not apply) this value:
Example (do this…)
vs. Counter-example (...not this)
When I see a problem, I take action or bring it to the attention of someone who can help.
When I see a problem, I ignore it because I assume someone else will take action.
When prioritizing my day, I focus on efforts that align with my team's goals.
I start new projects without referencing the existing goals of my team or other teams.
I make decisions based on reasonably available information.
I wait to decide until all possible data is available.
I make big, tough-to-reverse decisions in consultation with others.
I make big, tough-to-reverse decisions on my own.
When considering what to work on next, I typically prioritize ideas that have the biggest upside.
When considering what to work on next, I typically prioritize ideas that minimize bad outcomes.
When approaching a project or question, I make sure we have a single, empowered decision-maker.
I move so quickly that I do not define who needs to make the decision.
In my work, I consider a diverse range of end-user needs.
I avoid important input that might slow down or complicate a decision.
When I see a problem, I seek out the best person to address it before fixing it myself.
I seek to fix things right away, even if another person or team is more capable of doing so.
There are no rows in this table
🍃 Growth
We believe in constantly pushing ourselves to improve and achieve more, both individually and as a company.
For our team members, this means providing opportunities for personal and professional development, supporting their growth and progress within the company, and providing resources to help them continually learn and evolve.
For our product, this means continuously iterating and improving to better meet the needs of our users and stay ahead of the competition. We strive to innovate and evolve our product to provide the best possible experience for our clients.
And for our clients, this means providing them with the tools, resources, and guidance they need to grow and achieve their own goals. We view our clients' success as a key measure of our own success, and are committed to providing them with the support they need to thrive.
Overall, Growth is at the heart of everything we do at Yicom. We believe that by prioritizing growth in all aspects of our business, we can create a culture of constant improvement and achieve great things together.
Tips on how to apply Growth as a value
Example (Do this)
vs. Counter-example (...not this)
I actively seek out feedback and ideas from my team members, and value their input in decision-making processes.
I dismiss feedback or ideas from team members, assuming that I know best.
I proactively collaborate with colleagues from different teams or domain to solve problems and generate new ideas.
I only work within my own knowledge domain and don't seek out opportunities for cross-functional collaboration.
I communicate openly and transparently with my team members, sharing information and insights to build trust and foster a sense of shared purpose.
I withhold information or insights from my team members, either because I don't trust them or because I want to maintain a sense of control.
I actively listen to and consider different perspectives, even if they challenge my own assumptions or beliefs.
I dismiss or disregard different perspectives or opinions, assuming that my own viewpoint is the only valid one.
I prioritize team goals and objectives over my own individual priorities, and work collaboratively to achieve shared goals.
I prioritize my own goals or interests over those of the team, and work in a siloed or competitive way that doesn't contribute to the overall success of the company.
There are no rows in this table
🤝 Collaboration
Working together as a team leads to better outcomes and stronger relationships both within the company and with our clients. By fostering a collaborative culture, we can harness the collective talents and expertise of our team members to solve complex problems, make better decisions, and create a more innovative and inclusive work environment.
Plus, it’s way more fun that way !
Tips on how to apply Collaboration
Example (Do this)
vs. Counter-example (...not this)
I actively seek out feedback and ideas from my team members, and value their input in decision-making processes.
I dismiss feedback or ideas from team members, assuming that I know best.
I proactively collaborate with colleagues from different teams or domain to solve problems and generate new ideas.
I only work within my own knowledge domain and don't seek out opportunities for cross-functional collaboration.
I communicate openly and transparently with my team members, sharing information and insights to build trust and foster a sense of shared purpose.
I withhold information or insights from my team members, either because I don't trust them or because I want to maintain a sense of control.
I actively listen to and consider different perspectives, even if they challenge my own assumptions or beliefs.
I dismiss or disregard different perspectives or opinions, assuming that my own viewpoint is the only valid one.
I prioritize team goals and objectives over my own individual priorities, and work collaboratively to achieve shared goals.
I prioritize my own goals or interests over those of the team, and work in a siloed or competitive way that doesn't contribute to the overall success of the company.
There are no rows in this table
🔄 Trust
Trust is a foundational value. We believe that trust is critical for building strong, effective teams and delivering exceptional results for our clients. We approach trust in two ways: first, by starting with trust, assuming positive intent and building relationships based on openness and transparency. Second, by being trustworthy ourselves, consistently following through on commitments, communicating honestly and openly, and behaving in a way that demonstrates our integrity and respect for others.
Tips on how to apply Trust
Example (Do This)
vs. Counter-example (...not this)
I assume positive intent in my interactions with colleagues, even if we disagree or have different perspectives.
I assume the worst about others' intentions, and approach interactions with suspicion or hostility.
I'm honest and transparent in my communication with colleagues, even if it means admitting mistakes or sharing difficult news.
I withhold information or communicate in a way that is unclear or misleading, in order to protect myself or advance my own agenda.
I follow through on my commitments, delivering high-quality work on time and communicating proactively if I encounter obstacles or delays.
I make promises that I can't keep, or fail to deliver on commitments without communicating proactively with my team.
I respect the confidentiality of sensitive information, only sharing it with others on a need-to-know basis and following appropriate protocols for data security.
I gossip or share sensitive information inappropriately, without considering the impact on others or the company.
I'm consistent in my behavior and actions, treating others with respect and behaving in a way that aligns with Yicom's values and culture.
I act in a way that is inconsistent with Yicom's values, or behave in a way that is disrespectful or unprofessional towards colleagues or clients.
There are no rows in this table
🖼️ Transparency
We do our best work when we make projects, processes, and systems available to everyone who needs them—inclusive of our customers. Transparency promotes equity and inclusion within our team and customer base. So work in public. Have discussions in the open and document your work.
Transparency does not mean consultation or consensus on all decisions. In fact, an important form of transparency is clarity on who is responsible for a decision and who will be consulted.
Tips on how to apply Transparency
Example (Do This)
vs. Counter-example (...not this)
I keep team members informed of relevant information so that there are rarely surprises.
I hold back information until just before it needs to be shared, even if it is a surprise to my teammates.
I'm clear about what people should expect from me—even if that reality disappoints.
I obscure or minimize the truth in order to keep everyone happy.
I make it easy for others to follow my work by summarizing progress and decisions, and by sharing links to source material for deeper context.
I share raw notes with all details of my work, and expect others to make time to consume it all.
I communicate in clear, easy-to-understand language to help others engage with my work.
I use jargon or idioms that limit the impact and accessibility of my work.
I default to asynchronous methods to ensure the relevant people can access information.
I default to sharing information live, or in other ways that limit others' ability to access information.
When sensitive details come my way, I think twice and consult a manager before sharing publicly.
I share far and wide just for transparency's sake.
I use transparency to encourage a high standard of excellence for our work—for example, by publishing retrospectives.
I use transparency to call out or shame people who make mistakes.
I use transparency externally to build trust and momentum with our customers.
I hide my work from customers out of worry that competitors might steal it.
There are no rows in this table
➰ Iteration & Feedback
We believe in the power of iteration and feedback to drive continuous improvement and innovation. We know that the best solutions are rarely arrived at on the first attempt, and that ongoing feedback from stakeholders is essential to building products and services that meet the needs of our users.
We approach iteration and feedback by working in small, iterative loops, gathering feedback from all stakeholders as frequently as possible, and using that feedback to inform our next iteration. If an iteration fails to deliver value, we use the insights gained from that experience to learn and do better on the next iteration.
Tips on how to apply Iteration & Feedback
Example (Do This)
vs. Counter-example (...not this)
I break down large projects into smaller, more manageable tasks that can be completed within an iterative loop.
I take on large projects without breaking them down, leading to long delays and unclear progress.
I seek feedback from a variety of stakeholders, including colleagues, clients, and end-users, throughout the development process.
I assume that I know what clients or end-users want without seeking their input, or rely too heavily on a single source of feedback.
I use data and insights gathered from previous iterations to inform my approach to the next iteration.
I ignore feedback or data from previous iterations, assuming that my approach is the best one.
I remain open to changing course based on feedback and insights, even if it means pivoting away from a previously defined plan.
I stick rigidly to a predefined plan, even in the face of feedback or data that suggests a different approach would be more effective.
I learn from failures and use those lessons to inform future iterations, rather than dwelling on mistakes or trying to assign blame.
I blame others for failures or mistakes, or ignore failures without taking the time to learn from them.
There are no rows in this table
Want to print your doc?
This is not the way.
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.