So. Why DockYard?
Truthfully, this boils down to a pretty short answer. It doesn’t really need a full blog post. Don’t get me wrong: I’ve written one, and it’d be wonderful if you’d continue reading beyond the next sentence. But really, I sought out DockYard for two simple reasons: Trust and Quality.
Now, each of those terms is a huge umbrella, under which there’s space for ever so much context. So let’s start where one does, at the beginning.
I was born on April 22nd, 19…wait, too far.
Ok. My first job out of college was with a SaaS company, whose main product was a high quality, standardized database that contained all of the financial info you could possibly want about nearly every industry. They did what they did well, and - being headquartered in a college town - were pretty progressive. In my two and a half or so years there, I had about six different positions, one of which was to essentially beta test a huge, game-changing update to their flagship product.
I didn’t know it at the time, but that position had nearly all of what I would come to identify as qualities of my ideal job.
- Flexibility: I was given a specific but very high-level directive (“figure out where it breaks and how to make it better”), then trusted to deliver on it in whatever way worked best for me.
- Fulfillment: suggestions that my colleague and I made for improving the product were implemented on a near daily basis, making it easy to see the positive impact we were having.
- Respect: I was never micro-managed, second-guessed, or glossed over. That doesn’t mean I wasn’t challenged to defend my stances (or that I wasn’t occasionally just flat out wrong), but I always felt heard and valued.
- Growth: whenever I didn’t quite understand something, I was given the time and opportunity to learn about it. Mistakes or misperceptions were explained rather than simply dismissed with a quick “because X.”
- Stimulation: every day was different because I never knew what I’d find. That in and of itself made the work constantly engaging; I was never stagnant.
- Clear Communication: my manager was blunt - she managed 2 entire departments, she had to be. At the time, I had never experienced management of this ilk, and I was a bit taken aback…initially. Turns out, clear and direct communication is great.
- Principles: while plenty of my work directly contributed to making this product better, a lot of it never moved past the drawing board. Testing was rigorous, discussion and healthy debate occurred often, and sometimes, items got scrapped for the greater good. Saying “no” to a feature that would ultimately be detrimental to the product, even though it might seem cool, shows careful dedication to a set of principles that put Quality front and center.
Each and every one of these elements applies directly to Trust, Quality, or both. Trust meaning the trust your organization has in you, your ability to do your job, and your passion for doing so. Quality meaning the care with which both people, products, and the organization itself are treated.
That position only existed for about a year, but it had a big impact on me. I still list it on my resume.
I’ve since worked with four different organizations of varying sizes (from under 20 full-time staff, to thousands), at different levels of seniority, serving the multitudinous capacities that can fall within the realm of Project and Product Management. But especially relevant for this post: I’ve worked within many different teams and many different cultural settings.
Guess what? Nearly all the best things about any of my past roles can be summed up as the presence of Trust and Quality. And, coincidentally, nearly all the worst things about any of my past roles can be summed up as the absence of Trust and Quality.
Which, at last, brings me back to DockYard. As a 100% remote organization, they inherently bestow a massive amount of Trust upon each and every employee. And it’s palpable. Up until this point in this post, I’ve been an employee at DockYard for 5 whole days. During that time - in addition to the typical onboarding duties one undertakes when starting any new job - I have:
- better familiarized myself with GitHub’s project management and workflow tools.
- tested out a couple of different builds in staging.
- suggested a teensy enhancement to a product (which made it in time for our Progressive Web App example, High Tide’s, unveiling!).
- met up with some colleagues to cowork in person for an afternoon.
- identified a few areas in our internal workflow that can be improved (let’s see if future me gets it done!).
- started to get up to speed on four separate initiatives.
- added two custom emojis (emojii?) to Slack - perhaps my greatest achievement thus far.
- made it to here in this blog post.
Guess how many of those things I was asked to do. Go on, guess.
All of them!
No, I’m kidding. None of them! Seriously, none of them.
I was shown the ropes a bit, given some high-level info about what was going on and what was to come, and told to ask questions about anything at any time. I couldn’t wait to get started.
And that’s Trust. It motivates, it inspires, it makes you feel human.
Which leaves Quality. If you know anything about DockYard, you know our reputation for quality. I was lucky enough to have proof: one of my former companies worked closely with DockYard to create some amazing products. So, certainly as a client, I knew Quality was important to DockYard, and that was important to me. When you need something not just done, but done exceptionally well, it’s invaluable to be able to consistently rely on someone to deliver. That’s DockYard.
Internally, though, the value of Quality is much more multifaceted. It means a safe and enjoyable work culture. It means time and effort set aside specifically for you to work on what you want. It means real investment in your development and growth. It means a recognition of the complexities of everyday life, and not just the willingness, but the desire to support employees through their journey, as they support the organization through its own.
In short, it means someplace you actually do get excited about working for - and with - every day.
At least, five days in you do ;)