Vladimir Lovtsov / Leadership notebook
#management
Practice, analysis and observations on this topic.
Articles: 16
Analyst Days 14: Don't Paint the Grass — Data Risk in a BANI World
A reconstruction of my Analyst Days 14 talk on data quality and ownership: distinguishing a working control from attractive reporting.
Community Synergy: How a Large IT Company Can Use Its Own Expertise
How Tech Guilds helped me connect teams and knowledge. Reuse across a company, the structure of a Tech Hub, the economics of shared solutions and the conditions that make people want to participate.
Tech Lead: A New Challenge for an Analyst
Moving from analyst to project IT lead: building a team, establishing delivery practices, and discussing constraints with the business.
Hiring Signals from a Manager’s Perspective
Behavioural patterns, an interview radar and the manager’s own blind spots: assess working risks without pretending to diagnose a personality.
“Like FAANG,” Without the Cargo Cult: Bring the Context With the Practice
Architecture practices cannot be separated from scale, team structure, and operational maturity. Here is how to spot accidental complexity before adopting them.
Are Retrospectives a Waste of Time? Sometimes
When a retro becomes a ritual, how to restore its purpose, and why a change without an owner rarely improves anything.
Taking a Banking Product Real-Time
Lessons from an early real-time product built in 2023–2024: streaming architecture, production testing, and delivery decisions.
Can an Overly Detailed Specification Weaken Engineering Initiative?
A working hypothesis about the relationship between requirement detail, delivery predictability, and team autonomy.
Five Common Systems Analysis Mistakes on IT Projects
Common systems analysis mistakes on large banking and fintech projects: vague requirements, legacy integrations, regulation, failure scenarios, and late validation.
Building Fintech Products: Seven Paths to Production
A delivery map for banking products: team capability, governance, changing needs, infrastructure, cross-team contracts, the delivery platform, and operations.
User Stories: From Need to Acceptance Criteria
How to frame a user story around who, what, and why, add testable acceptance criteria, and avoid turning it into a miniature specification.
Saint HighLoad++ 2024: Moving a Banking Product to Real-Time
How Vladimir Avramov and I turned an early real-time product built with Flink, Kafka, and Tarantool into a focused technical talk.
Building an IT Team Fast: Risks and Benefits
How to speed up hiring without pretending speed is free: what to test before the offer and how to reduce early hiring risk.
IT Conferences for Analysts: A Practical Guide
How to choose an event, prepare useful questions, and turn a talk or visit into durable professional connections.
How a Software Development Team Actually Works
One practical model for software delivery from discovery to release: six overlapping stages, common roles, and the team’s shared responsibility for outcomes.
How to Interview a Client When You're the Analyst on an IT Team (a Checklist)
A step-by-step algorithm for interviewing a client when there is no business analyst on the team: preparation, running the interview, analysis, and confirming requirements.
No articles found. Try another phrase or select all topics.
Short observations and new writing in my Telegram channel (in Russian).
@it_underside ↗