Why
We exist to enable innovation that continues to redefine our organization’s future. We also support the structures and systems of our teams now in the present. Our “job to be done” or purpose is to remove obstacles to productivity and reduce frustrations with technology to enable our teams to deliver their best work.
To achieve this we endeavor to deliver endpoints and services that are feature rich, quick, stable, and secure. To scale our organization teams should be able to onboard new team members as quickly as possible. We should be partnering across our organization to build scalable, well understood technical processes.
Who
To scale our platform to support 15million monthly active users we must retain and attract passionate, talented people to our organization. Highly capable people build highly capable products and teams. However, highly capable people despise red tape and corporate bureaucracy. They want to get a job done as efficiently and effectively as possible.
What
It is no surprise that our organization continues to opt for platforms and devices built around a first class user experience. We are passionate about our platforms, but only insofar as they enable us to achieve our goals and are in alignment with our culture. We require tools and systems that are highly capable and easily usable.
Apple excels at understanding the job to be done and building a technology to help. So we are a Mac shop now and must build teams and partnerships to support this platform. Corporate IT structures tend to be far removed from understanding the context and needs of their customer therefore the systems and processes they build do not prioritize user experience. This is why we directly manage and influence the direction of our fleet of devices. We are in the best position to support our teams because we are integrated into the body.
Our intent is to resist the scope creep and overreach of decisions made without context or consideration for the impact to our teams. Where compliance and audit regulations require specific controls on endpoints we want to be involved in the selection and implementation of those solutions to reduce any potential for negative impact with the user’s experience.
How
When a software tool or process is not used by the whole organization then we should be identifying owners within the team that have a stake in the tool’s use. We cannot own and manage everything and so we seek to encourage a high level of partnership with our teams. Our model of partnership should be to assist in early implementation and documentation, but shift the majority of support to key members within the team using the tool.
For software tools or processes used across the organization we tend to provide a higher level of care and feeding to maintain and manage the platform or process.