# How I work Source: https://manaienko.com/how-i-work/ Author: Artem Manaienko # How I actually _work._ How I help people grow, make delivery decisions and work through technical problems. These pages come from things I have done, including mistakes I still think about. Show[Everything12](#everything)[People02](#people)[Delivery04](#delivery)[Economics01](#economics)[Platform01](#platform)[Applied AI04](#ai) People and leadership only. Showing 2 of 12 practice pages. Product and delivery only. Showing 4 of 12 practice pages. Technical economics only. Showing 1 of 12 practice pages. Platform and architecture only. Showing 1 of 12 practice pages. Applied AI only. Showing 4 of 12 practice pages. ## People and leadership - [Leadership selection · Succession · People leadership**How I select and grow technical leaders** The strongest engineer is not automatically the right lead. I give candidates real work with a team and watch how they delegate, take responsibility and communicate. Wider leadership needs the same practical preparation. ↗](https://manaienko.com/how-i-work/selecting-technical-leaders/) - [People development · Coaching · Autonomy**How I develop engineers** At Teladoc I had no promotions to offer my contractor team. I measured growth through the scope people could own, the ambiguity they could handle and how independently they could deliver. ↗](https://manaienko.com/how-i-work/developing-engineers/) ## Product and delivery - [Prioritisation · Product and engineering · Capacity**How I turn business priorities into a backlog** I start with the business outcome, cost of delay, risk and available capacity. Then I turn that into the smallest useful engineering work, with clear priorities and a way to check the result. ↗](https://manaienko.com/how-i-work/business-priorities-into-a-backlog/) - [Delivery · Operating models · Change**How I handle delivery when scope keeps growing** At ASKfm, we spent about six months on a two-month MVP. The feature worked, but I still see the delivery as a failure. We kept rebuilding while the requirements changed. I should have forced the scope and date conversation much earlier. ↗](https://manaienko.com/how-i-work/delivery-when-scope-stops-being-honest/) - [Engineering leadership · Operating models · Change**How I explain decisions people will not like** I want people to be able to tell me I am wrong. Especially when a decision makes their work harder. I explain the problem, listen before the decision is final, and make time for the people who would rather talk privately. ↗](https://manaienko.com/how-i-work/decisions-people-dislike/) - [Engineering effectiveness · Delivery · Operating models**How I measure engineering effectiveness** I look for the real cost and bottleneck across the delivery workflow, including work outside the ticket. Then I need a baseline and a comparison that keeps speed, quality and cost together. ↗](https://manaienko.com/how-i-work/measuring-engineering-effectiveness/) ## Technical economics - [Technical economics · Executive communication · Forecasting**How I report results, including the misses** I want to be able to explain the numbers I use, including the ones I got wrong. That means showing what I expected alongside what happened, and dropping a good-looking claim when I can no longer support it. ↗](https://manaienko.com/how-i-work/reporting-results/) ## Platform and architecture - [Application platform · Design systems · Cross-team delivery**How I run a platform other teams depend on** I run shared platforms as internal products. That means agreed contracts across teams, predictable release and migration rules, and explicit choices about reliability, flexibility and the scope we can support. ↗](https://manaienko.com/how-i-work/platforms-other-teams-depend-on/) ## Applied AI - [AI-enabled engineering · Delivery · Quality**My agent delivery harness** I built NADILI's delivery harness to coordinate coding agents through planning, independent review and checks. I approve the plan and start the work. ↗](https://manaienko.com/how-i-work/agent-delivery-harness/) - [AI-enabled engineering · Developer experience · Adoption**How I put AI into a delivery system** I build shared workspaces with repository context, a knowledge base and a workflow for each delivery stage. Engineers review the outputs at the points where a wrong decision would be costly. ↗](https://manaienko.com/how-i-work/ai-in-the-delivery-system/) - [AI-enabled engineering · Delivery · Quality**AI across the SDLC** AI across delivery needs shared context, specifications and checks around the model. Here is how I would build that environment, use it at each stage and decide where more autonomy is justified. ↗](https://manaienko.com/how-i-work/ai-sdlc/) - [AI-enabled engineering · Technical economics · Quality**How I compared two code-review models** I wanted to choose one review model. After ten paired reviews, I kept both. The faster one cost less per review, even at a higher token price. The slower one found enough additional defects that I did not want to lose it. ↗](https://manaienko.com/how-i-work/code-review-model-experiment/)