How I think about technology
Three lenses I use to weigh every decision
I am an IT solutions architect,
who treats technology as a tool for building operational capabilities – not as an end in itself (you can find my full CV and career path on the About me page).
This site doesn't sell anything – it shows how I work. I weigh every technology decision through three lenses: predictability, technology risk, and impact on margin. Below I describe what that means in practice – the full breakdown of the technical competencies behind it is on the My Competencies page.
Where I can support
The three lenses are not slogans. They translate into specific areas I work in every day:
Predictability
Before anything gets built, I check whether it can be built within the assumed time and budget: I verify feasibility, break the scope down into measurable pieces, and make sure the architecture is realistic and scope changes stay under control. Underestimation and scope creep usually come from decisions made too early.
Technology risk
I look for places where a project depends on a single person, on architecture no one understands, on unstable releases, or on environments that cannot be reproduced. That is where I work on architecture and technical debt reviews, stabilizing projects in crisis, and CI/CD standardization.
Impact on margin
Rework, manual processes, deployment errors, and architecture that needs too many seniors are costs that only show up over time. That is why I look at project profitability, automate processes, and design architecture for the cost of maintenance, not just the first release.
Want to see the full list of technical competencies behind this? See My Competencies
Most often I support teams in system architecture, infrastructure and DevOps, security, AI/LLM, and e-commerce with automatic order fulfillment – in design, implementation, and optimization of existing solutions, in technical consultations, mentoring, and training. Both in longer projects and in short technical conversations.
Projects that interest me
I am not looking for contracts. I am interested in projects where:
- technology really matters – architectural decisions determine whether the product works, scales, and makes money,
- the goal is ambitious – something new, hard, or something nobody has done well yet,
- the right people are involved – a team that wants to understand, not just ship, and for whom predictability, risk, and margin matter as much as features.
Building something like that? I am happy to talk. Write to me • View Technologies • View My Competencies