Welcome to Atlassian IT’s Product-centric Operating Model (POM)! Before diving into the nitty-gritty details, this page serves as your guide to all things POM in Atlassian IT. You can find information on why we decided to embrace this operating model, how this model will change our operations, and what this means day-to-day. For the nitty-gritty details, we invite you to explore the POM pages under this one.
...
| Info |
|---|
In brief Why are we re-defining our operating model?
How does this change the way we operate today?
What else are we sharing about our journey and how we’re organizing ourselves now? Project to Product Operations |
Why are we becoming a product-
...
centric IT Organization?
To date, we have done great work to improve the foundation of IT processes but we have primarily executed in a project-based delivery model where we established our practices around project definition, requirements gathering, funding estimates, resource tracking, and timelines. Today, we recognize that the pace of work continues to accelerate and that we need an operating model that allows us to be more dynamic while operating at speed and scale.
IT will need to become more product and value-driven, focusing beyond the transaction of a sale toward the longer-term customer relationship to continue delivering amazing customer and employee experiences as demand grows. As an agile and forward-thinking IT team in a rapidly growing company, we need to modernize IT for our company and customers and design IT for the future.
Our product-centric operating model will allow business and IT to work together to navigate a dynamic competitive landscape, a seemingly infinite set of digital tools, and shifting stakeholder demands. We will adopt a product mindset, with product owners who not only drive continuous improvement but innovate and experiment, while using data that help us make informed decisions.
...
What is an
...
operating model?
An operating model defines how an organization positions its people, process, and technology to deliver value to both internal and external customers.
Here’s the breakdown
A product is a capability, brought to life through technology, business process, and customer experience, with a continuous value stream and an ability to measure success independently
A product-oriented centric operating model, then, is one in which IT resources are organized around business capabilities or “products” instead of specific IT systems (e.g. SAP, CRM) or functions (QA, Engineering, Infrastructure).
Products as a Serviceservice, on the other hand, are centralized, service-focused teams providing services needed across all products and the entire value chain to create scale and drive consistency across the entire organization.
The trend towards product-centric operating models personifies the recognition that IT is critical to business success and that it should be managed just like a traditional product or service.
...
What’s changing?
We are moving away from a traditional IT operating model to a Product-based Operating Modelproduct-centric operating model, where our teams will be aligned to core IT products and platform offerings.
From | → | To |
|---|---|---|
Projects with definitive start and end dates | Products that are constantly improving and maturing | |
Heavy list of requirements, all of which are delivered at the end of the project | Rapid, iterative delivery against requirements | |
Lack of ownership around outcomes | Accountable teams with clear, outcome-oriented goals | |
Reactive planning and engagement with the rest of the business | Strategic partnerships with stakeholders and collaborative product roadmaps | |
Specialized engineers that go where-ever their skills are needed | Full-stack engineers with T-shaped expertise |
It’s all about the mindset
This model will allow us to adopt a product mindset, with product teams who not only drive continuous improvement but innovate and experiment, while using data that help us make informed decisions. Product Managers will develop a product strategy and roadmap in lockstep with the business that clearly articulates how they will mature the product to better meet customer needs and optimize competitive positioning.
...
Each of our product teams is responsible for identifying opportunities for innovation in their domains. We will look to the intersection of employee behavior and the tools and technologies our teams use to deliver a continuously improving employee experience.
Our new operating model will increase capacity for change through accountability with clear roles and responsibilities in our product teams.
Tighter alignment with our business teams to articulate product vision and create adaptive roadmaps that drive business outcomes and can respond to changing business needs.
Consistency in our operating rhythm and measures of results: product team health, product performance, and business outcomes, which will allow for greater accuracy in forecasting.
Things we’re still figuring out
We believe this is a step in the right direction, but we also acknowledge that we are in the middle of this journey and still have work to do before we are fully operational. While we’ve got the basics down, there are still details to be ironed out in the following areas:
Workstream | Description |
|---|---|
Product management | What it means to be a product manager in Atlassian IT including mindset, roles, and core PM practices. |
Delivery, architecture, and technical enablement | How we delivery work across the organization including our rhythms, artifacts, tools and metrics. Includes engineering practices as well as product mgmt. |
Skills and people | Ensuring our roles collateral is finalized and conducting gap assessments on the roles and people we have today. |
Culture and change | Develop training and communication plans to keep the rest of Atlassian up to speed on POM. |
Strategy and business alignment | How we engage with our business partners and develop strategic business proposals. |
Portfolio & Funding | Finalize aligning our portfolio and funding model to our operating model. |