HealthJoy Engineering Divisions — Alignment & Autonomy

With software engineering a team endeavor, our purpose, vision, and mission depend not only on the unique strengths of each division, but also on high collaboration across all engineering divisions. We embrace a lot of system thinking to balance each division’s autonomy and alignment across the board.

How We Work Together

Our engineering purpose aims to help all engineering divisions to collectively focus on the things that will help our department become more valuable to the rest of our company, and serve the business’ explicit and implicit needs, now and in the future. Our compass — consisting of four measures of Throughput and Stability — helps all engineering divisions align and connect for rapid growth, balancing between efficiency and effectiveness.

Every quarter, all engineering divisions align their quarterly focus with the company’s quarterly goals. By doing so, we enable all divisions to connect the strategic HOWs of engineering with the strategic WHATs for the business. All engineering divisions leverage OKR superpower “Align & Connect for Teamwork” for cross-functional interdependencies/OKRs across the engineering divisions, as John Doerr presented in his book Measure What Matters. Throughout the quarter, all engineering division heads come together as one cross-functional team to continually reconnect and realign for the cross-functional OKRs, while leveraging another OKR superpower “Track for Accountability.”

How We Strive for Excellence

Our strategic practices enable all of our divisions to paint their own canvas utilizing the tools, technologies and engineering best practices that make each division awesome. Using the framework from Toyota Improvement Kata, each division systematically moves forward from their current state to the next target condition, toward awesomeness for the division. Each division’s team members use our compass and the elite levels for throughput and stability to make their respective division’s mission meaningful, and define how it contributes to the bigger engineering vision.

Each division is empowered to define the awesomeness for the division as a long-term strategy. By giving team members the freedom to unleash their creativity and live their dreams, each division owns its own Big Hairy Audacious Goal (BHAG), as Jim Collins presented in his book Good to Great. The BHAG for a division is basically its mission. Each mission drives not only what’s best for the corresponding engineering discipline, but also the best cross-functional team endeavor for software engineering as a whole.

Like what you’ve read? HealthJoy’s engineering team is hiring across divisions. Visit our careers page to learn more.

Architecture Mission

  • Engineering creativity to, and validation of, business solutions
  • Architecture-enabled parallel development
  • Architecture-driven, long-term and short-term product delivery plans
  • Architecture-empowered coding
  • Architecture-enabled parallel delivery

Development Mission

  • Developing innovative technical solutions that give lasting business values
  • Rapid delivery of product ideas without building up tech debt
  • Delivering secured and high-quality products
  • Uncompromised product stability and recoverability

QA Mission

  • Reducing risks associated with low-quality requirements
  • Earliest feedback to developers at every stage of SDLC
  • Safeguarding stability of existing functionalities
  • Enabling developers to maintain quality with minimal human intervention

DevSecOps Mission

  • Own the infrastructure for HealthJoy products
  • Enable developers to deliver product without human intervention
  • Institute guardrails and traceability for secured and reliable product delivery and support
  • Offer best insight into system and product health

Project Management Mission

  • Long-term and short-term projections for product initiatives
  • Measuring and reducing long-term and short-term risks to product delivery
  • Reducing business impact caused by critical production issues
  • End-to-end transparency to all change contributors and stakeholders
  • Growing Product Teams as highest performing teams

IT Mission

  • Own all IT assets through the lifecycle of the asset
  • Provide best and scalable customer service for the entire lifecycle of IT solutions
  • Manage and execute IT policies for the lifecycle and use of IT assets
  • Provide high transparency to the quality of IT solutions and IT service desk

Our engineering divisions use their missions to drive their team’s long-term strategy, as outlined in our Engineering Strategy Playbook. Together, all engineering division missions help form our overall engineering mission for global outcomes and enable divisions to align and connect with one another.

In the next HealthJoy Engineering post, we’re going to share more insights into our Architecture Mission.

Visit our careers page to learn more about open roles on HealthJoy’s engineering team.

--

--

--

Notes from HealthJoy’s engineering team as they pursue our vision: to remove the complexity from being healthy and well.

Recommended from Medium

How I installed /e/ on my Samsung Galaxy S7

5 Best macOS Apps for a Productive Workflow

Cloud Native vs Knative for beginners!

Using the Tag System in Unity and Damaging the Player

Turn Your Old Zombie Laptop into a Slick Chromebook

What is the OSI Model? 7 layers explained in detail

BUILDING KNOWLEDGE: 15 parts, 37 screws, 6 beta tests yields 1 desk

tools and office supplies arranged in a circular pattern

Quantum Programming by abstracting ourselves from Quantum Mechanics: Abstraction level 0

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Sajal Dam

Sajal Dam

Sajal Dam is CIO at HealthJoy where he focuses on providing engineering solutions that guide members to affordable, high-quality healthcare.

More from Medium

Engineers had a week to choose their adventure. They chose open source.

Let Others Solve Your Problems: Change Your Mindset From APIs to SPIs

Constant work to onboarding new members into engineering team

We took The Pragmatic Engineer Test (and scored 12 out of 12!)