Service

Technical Leadership for IT Projects

If you have several IT and development projects running and nobody watching all of them, that is the job I do. I look after the projects overall: architecture, code quality, releases, servers, vendors and delivery.

What I take on

Reviewing what exists and saying plainly what is at risk. Setting the technical direction across apps, web and back end. Planning work in two-week sprints. Reviewing code. Mentoring developers. Keeping an eye on hosting, security, domains, email and third-party vendors so nothing important belongs to nobody.

How I keep projects honest

Working software every two weeks, a written update instead of a status meeting, and a measurement before anyone says a thing is done. If a release is at risk, you hear it from me early, along with the options.

Who it suits

Companies with an in-house team that needs senior direction, founders who are not technical and want one accountable person, and businesses whose IT grew project by project and now needs someone to pull it together.

Questions

Do you replace my developers?

No. I work with the team you have, raise the standard of what ships and step in on the hard parts myself.

Do you still write code?

Yes, every week. I would not trust a technical lead who has stopped, and neither should you.

Can you audit a project before committing?

Yes. A short written review of the code, infrastructure and risks is a good way to start.

Related projects

Technical Leadership for IT Projects: let's talk

A discovery call within 48 hours, and a kickoff typically inside two weeks.