reporting lines is a project management site for people who actually deliver things. Not aspirational methodology. Not certification prep. The practical stuff that keeps projects moving when reality diverges from the plan.
Who writes this
I'm Simon Inglis — a programme manager and delivery leader based in Brisbane, Australia, with 20+ years in enterprise IT.
Most of that time has been in government and healthcare — environments where the governance is heavy, the stakeholders are many, and the consequences of failure are public. Programmes worth tens of millions of dollars, affecting many thousands of users across geographic areas as large as continental Europe. I've recovered programmes that were already in trouble when I arrived, and learned (often the hard way) what makes delivery work in complex organisations.
Domains
Most of my career has been in healthcare and government IT, delivering across enterprise medical imaging, electronic medical records, pharmacy systems, pathology and sleep lab information systems, vaccine management, clinical messaging and integration via enterprise service buses, and connections to national systems including the My Health Record. Also enterprise telephony, time and attendance, customer experience platforms, billing and revenue, and clinical risk management.
Before healthcare — travel, utilities, telecommunications, and knowledge management. Ticketing and booking systems, network asset management, and tender preparation for critical communications infrastructure.
What you'll find here
- Recovery patterns for troubled projects
- Governance that helps instead of hinders
- Stakeholder management for complex environments
- Risk frameworks that surface real problems early
- How PM, BA, test, change, and architecture roles support each other in delivery
The approach
Every piece of guidance comes with criteria — when to apply it and when to skip it. "It depends" isn't an answer unless you say what it depends on.
Contact
Best way to reach me is via LinkedIn.