Every company I have worked for has had a set of core values that helped shape that company’s culture. Affinity is no different. It has five core values that have been fundamental to the company since it was founded. Everyone at Affinity adopts and uses these values to help guide their everyday actions, and they have […]
Every company I have worked for has had a set of core values that helped shape that company’s culture.
Affinity is no different. It has five core values that have been fundamental to the company since it was founded.
Everyone at Affinity adopts and uses these values to help guide their everyday actions, and they have become an important part of what it means to work at Affinity. This was apparent to me from the first day I joined and has truly resulted in a supportive working environment.
We recognize that our teammates are people who have strengths, weaknesses, dreams, and life stories.
Prior to joining Affinity, I had expressed my interest in being the type of designer who works with code.
The design team encouraged me in this and helped me contact the developers who could give me the proper Github access and set up my local dev environment. Although working with engineering was something I was passionate about, it felt like everyone on the design team was as invested as I was.
We are team players who empower our teammates to do their best work.
From past experience I know that getting a local dev environment running outside of the engineering team isn’t always the smoothest process.
To my surprise, Affinity had a thorough Getting Started guide tailored to designers, which kickstarted the setup. Over the next couple of days, as I encountered technical issues, our engineers went out of their way to help me troubleshoot them, responding to my Slack messages or jumping on a quick Zoom call.
With the help of the design team and the engineers, I was able to get my environment up and running in no time.
We care deeply about delivering exceptional work and we take ownership over our results.
Soon after getting settled, I was introduced to the UX backlog. This Asana board is a design team-driven initiative to make sure we track design debt as reported by internal and external people.
Keeping a bug backlog is common, but the UX backlog was new to me and shows how committed Affinity is to continuously improving the platform so that it offers a polished, high-quality experience.
We are dedicated learners and teachers.
Much of my development experience comes from working on personal projects, and because of this, I do not have much experience working within coding standards and using a proper GIT workflow.
Over the course of my first few pull requests, engineers took time to walk me through Affinity’s coding standards and the pull request review process.
This helped me become a better developer and taught me how to work within a community of designers and developers to reach common goals while maintaining high standards.
We value ideas over titles and believe that the best ideas can come from anywhere.
Of the companies I’ve worked for, I’ve yet to work anywhere that has had such a progressive approach when it comes to individual roles and responsibilities.
Often designers who can help with engineering in some capacity are not allowed to do so because it is not their actual job. But Affinity encourages individuals to contribute, work toward their strengths, and make an impact regardless of their title.
How Affinity’s Core Values Optimized My Onboarding Experience was originally published in Affinity on Medium, where people are continuing the conversation by highlighting and responding to this story.