Planet Argon Company Goals
This page explains Planet Argon’s 3-year and 1-year company goals and how the Engineering Team will help the company achieve those goals.
This page also includes a list of our current Team Initiatives, with links to their relevant pages in this handbook.
Company Goals
Section titled “Company Goals”3-Year Strategy
Section titled “3-Year Strategy”Our 3-year stragegy looks forward to July 2026, setting fiscal and organizational goals for the company and providing measurables and roadmaps to keep us accountable and ensure we meet these goals.
Fiscal Goals
Section titled “Fiscal Goals”- Target Revenue: $3.5m to $4m
- Profit: 25%
- Fixed-Cost Project Revenue: 20%
Organizational goals
Section titled “Organizational goals”| Goal | Reasoning |
|---|---|
| 1. We have self-organizing teams with multiple PMs | To better focus on client needs and sales opportunities by spreading the project management work among different teams |
| 2. We have documented a scheduled role advancement plan for teams | To ensure developers know what is expected of them within their role and understand what it will take for them to advance to their next role |
| 3. We have a more geographically diverse set of clients | To ensure that we will not be overly impacted by regional economic conditions |
| 4. We are seen as a great example of an organization that can sustainably recruit and retain developers and contractors of varying skill levels | To open up more opportunities for people entering our industry |
Measurables
Section titled “Measurables”| Measurable | Reasoning | Related Goal |
|---|---|---|
| Team-reported DX snapshot scores are at or above 90% of industry standard | High or upward-trending scores show movement towards creating the satisfying and inclusive work environment we aim to be | 4 |
| Current team has completed one 18-month Scheduled Role Advancement Plan | Completion of role advancement plans ensures developers understand the responsibilities of their current role and what’s required of them to advance | 2 |
| 25% of sales opportunities are via referrals | Referral-based sales demonstrate the value we provide to our clients | Revenue goal |
| 25% of opportunities are via outbound sales | Outbound sales leads demonstrate our ability to proactively attract clients | Revenue goal |
1-Year Strategy
Section titled “1-Year Strategy”Our 1-year stragegy looks forward to July 2024, setting fiscal and organizational goals for the company and providing measurables and roadmaps to keep us accountable and ensure we meet these goals.
Fiscal Goals
Section titled “Fiscal Goals”- Target Revenue: $1.7m
- Profit: 25%
- Project-Based Revenue: 50%
Organizational Goals
Section titled “Organizational Goals”| Goal | Reasoning |
|---|---|
| 1. Hire a FT/PT Junior Project Manager | To allow us to better scale our project management resources and take on more projects |
| 2. Rank in Inc.com’s “2024 Best Places To Work” list | To demonstrate our continued dedication to fostering a satisfying, enjoyable, and healthy work environment |
| 3. Reduce our cost to produce the Maintainable podcast | To generate revenue to help cover some of the costs of producing the podcast |
| 4. Centralize client/developer tools | To reduce costs for the company and reduce the number of tools we are asking our developers and clients to use |
| 5. Reduce the number of sales/marketing apps we use | To reduce costs for the company and consolidate our client details and contact infomration into a single location |
| 6. Replace the annual Rebase with structured quarterly events | To increase engagment with the team, simplifiy scheduling, and encourage contractors to participate in one event per quarter |
| 7. Increase our clients’ technical knowledge | To increase sales by encouraging clients to come up with new project ideas or feature requests |
| 8. Improve our sales process and materials | To attract more qualified leads and improve sales conversion rates |
| 9. Launch a new version of the Rails community survey | To improve the way we show survey data and the history of that data |
| 10. Simplify dev environment set-up | To create a scalable, reliable onboarding process for new developers |
| 11. Create a uniform deployment process for client projects | To make it easier and faster for more developers to deploy projects safely and more often |
| 12. Ensure clients use templates when creating new issues | To guarantee necessary context and requirements are provided on each issue |
| 13. Audit client spends on project tools and utilities | To demonstrate our value by reducing their costs of doing business |
| 14. Re-launch webinars, seminars, coaching | To supplement project-based revenue by offer a fixed-cost service with a lower price point |
Measurables
Section titled “Measurables”| Measurable | Reasoning | Related Goal |
|---|---|---|
| Team-reported DX snapshot scores are at or above 75% of industry standard | To demonstrate advancement towards the completion of 3-year goal #4 | 4 |
| Launch and host 4 new services or products | To diversify our revenue sources and offer more entry-point products that can be later converted to retainer clients | 8, 14 |
| 25% of opportunities are via outbound sales | Outbound sales leads demonstrate our ability to proactively attract clients | Revenue goal |
Team Initiatives
Section titled “Team Initiatives”Our team initiatives are goals identified by the engineering manager and discussed in the Engineering Team Meeting. The manager owns each, but parts or whole initiatives can be delegated to individual or multiple team members.
| Initiative | Reasoning | Progress |
|---|---|---|
| 1. Move all project repos from Bitbucket to Github | Using just one version control tool reduces task switching and allows developers to become more skilled with that specific tool | ✅✅✅✅🔲 |
| 2. Move CI/CD Pipelines to GitHub Actions | Using just one CI/CD tool reduces task switching and allows developers to become more skilled with that specific tool | 🔲🔲🔲🔲🔲 |
| 3. Increase code coverage across all project repos | Improving test coverage will improve the stability of our client applications and give devs more confidence when deploying code | ✅🔲🔲🔲🔲 |
| 4. Standardize QA Process in SDLC | Designing an official QA process will lead to more stable and robust client apps | ✅🔲🔲🔲🔲 |
| 5. Standardize Deployment Safeguards | Implementing deployment safeguards will allow more developers to deploy their work confidently and will allow for easier rollback should bugs be introduced to production | 🔲🔲🔲🔲🔲 |