About

Connected systems for the places people live and work.

Sydney. Microsoft and Azure first.

James Park, Solution Architect at ARK360
James Park, Solution Architect, Sydney
James on LinkedIn

Profile

What I do.

Solution Architect focused on Microsoft cloud adoption, governance and customer success. I work with CIOs, platform managers and stakeholders to turn Microsoft investment into capability people use. Much of my work happens after the architecture is agreed: driving adoption, setting up governance teams will follow, and keeping executives, delivery teams and risk owners aligned.

At ANSTO, a federal science agency, I owned the Microsoft 365 and Power Platform estate end to end as Team Leader and Product Owner. I built the centre of excellence from the ground up and improved adoption of the intranet, all under ISM and IRAP controls.

Before that I was an embedded Microsoft consultant in property and construction, partnering with a construction CIO on an Azure data hub and working inside an ASX-listed property group's digital team.

Today, through ARK360, I work with client CIOs and platform managers as strategic advisor, architect and delivery lead. I measure success by adoption, and by whether the capability survives after I leave.

Career

Roles I have held.
Newest first.

  1. 01

    Solution Architect, ARK360

    Jul 2024 to present. Advisor to a civil construction client.

  2. 02

    Team Leader and Product Owner, ANSTO

    Jul 2022 to May 2024.

  3. 03

    Microsoft Consultant, Mirvac

    Nov 2017 to Jun 2022.

  4. 04

    Microsoft Consultant, ADCO

    Nov 2017 to Jun 2022.

  5. 05

    Digital Application Developer, Mirvac

    Apr 2014 to Sep 2017.

  6. 06

    Technical Consultant, EPM Partners

    Nov 2011 to Apr 2014.

  7. 07

    Software Developer, Emotum

    Jan 2006 to Nov 2011.

Where things stand

A portfolio I can show.
Where I stand.

What this site is
Purpose, principles and work I can show.
How I work
Microsoft and Azure first. A person stays accountable for consequential decisions. Systems are owned by the people who use them.
What I will not do
Send anything without a person's approval. Certify compliance. Hide how an output was produced.
Relevant experience
Almost twenty years building systems.

The principles I try to keep