Corporate culture has long ceased to be an ephemeral concept from HR presentations, turning into a decisive factor in the battle for talent and operational efficiency. Creating an environment where innovation and trust thrive requires not declarations, but subtle engineering work with human systems. Polina Semina is that extraordinary and talented leader who, with her approach, broke a breach in the wall of bureaucratic inertia and proved that culture can be managed as precisely as business processes. Being at the cutting edge of the industry, she embodies a locomotive leading followers, and a true guru of her craft, capable of reaching the peaks of the industry in a wide range of fields.
– Polina, hello. In the world of large corporations, it is customary to speak about culture in terms of large-scale programs and multi-page codes. However, one of your most high-profile initiatives at T1, the “Help Window,” sounds deceptively simple. What was really behind this idea of short morning meetings?
– Hello. That’s correct, the simplicity here is only the external shell. The “Help Window” is not just meetings; it is a tool for targeted impact on the system. I would call it managerial acupuncture. Instead of launching a cumbersome and expensive transformation program, we created a single entry point, one channel with a minimal access threshold, through which any employee could convey their problem, idea, or pain directly to the decision-making level. The idea was to create a mechanism that would, in real time, uncover hidden inefficiencies, bureaucratic deadlocks, and team frustration points. It was a way to obtain honest, unfiltered feedback and immediately turn it into managerial action.
– What specific “pain” or systemic failure in the corporate machine of an IT giant did you diagnose, that made the solution precisely the “Help Window” rather than, say, a new regulation or another dashboard?
– I diagnosed a symptom that I call “organizational cholesterol.” It is the accumulation of small, unresolved problems that individually seem insignificant, but together clog the informational arteries of the company. Approval of a simple document drags on for weeks, a resource request gets lost between departments, a good employee idea dies at the level of their direct manager. All this generates hidden tension and reduces the speed of the entire system. A new regulation would not have helped here; it would have been just another instruction that nobody reads. The “Help Window” was intended to work like a surgical instrument: it did not treat the entire system at once, but selectively removed these “plaques,” restoring healthy circulation of information and decisions.
– Simplicity is often the most difficult to implement. What was the mechanics of these meetings? Were there rules that turned a short conversation into an effective tool, rather than just another formal “briefing”?
– The mechanics were strict, despite the informal nature. First, regularity and accessibility: weekly, at the same time, in an open format. Anyone could come. Second, strict timing: 15–20 minutes for the whole session, 2–3 minutes per case. This forced participants to formulate the essence of the problem clearly and without unnecessary “fluff.” Third, and most important rule – a “no-blame zone.” We were not looking for who was guilty; we were looking for a solution. The question was always: “What can we do right now to fix this?” Fourth – immediate action. The problem was either resolved on the spot, or I took responsibility for escalating it to the appropriate level with a specific deadline for resolution. This created confidence among people that their voice was not only heard but had real consequences.
– High engagement is a good indicator, but business thinks in terms of results. How did the effect of the “Help Window” translate into real, measurable improvements for the department and the company? Can the ROI of empathy be calculated?
– The ROI of empathy can be calculated if translated into business metrics. The direct effect we saw was in process acceleration. For example, document and payment approval times, which were previously a headache, we managed to reduce by more than 40%. This is not empathy; this is pure operational efficiency. An indirect, but no less important effect, is problem prevention. In these meetings, we identified risks at an early stage when solving them required minimal effort. How much money and time did we save by avoiding potential failures? That is the ROI. In addition, we gained a channel for grassroots innovation. Several ideas for optimizing document flow and reporting, which reduced team workload by 30%, came precisely from there, from rank-and-file coordinators. This is pure profit derived from trust.
– Is this approach to creating open communication channels your universal method? Do you apply its principles now, when building culture from scratch in your American projects, for example, in the tech startup Gmotion?
– It is a fundamental principle that adapts to the context. In a large corporation, it takes the form of a structured initiative like the “Help Window.” In a startup like Gmotion, or in small service companies that I manage, this principle is embedded in the DNA of daily communication. We do not have formal 15-minute meetings because all our work is one continuous “Help Window.” We use Slack, short daily meetings, an “open door” policy in the most literal sense. But the essence is the same: maximum speed of information flow, zero tolerance for hiding problems, immediate reaction, and a focus on resolution. Creating such an environment from scratch is a luxury that large companies do not have. But the principles remain exactly the same: trust through transparency and speed.
– Surely in a large structure there were skeptics who considered such “conversations” a waste of time. How did you overcome possible resistance and prove the value of informal communication in a world obsessed with KPIs and strict deadlines?
– Skepticism is a natural reaction of a system to changes. I did not spend time trying to convince skeptics with words. My argument was results. When one such 15-minute meeting helped solve a problem with a contractor, which had been “hanging” in emails for weeks and slowing an important project stage, the fiercest skeptic saw its value. When an employee, instead of quietly sabotaging an inconvenient process, came and suggested how to improve it, and we implemented it within two days, middle managers realized that this is a tool for them too. I did not fight a culture obsessed with KPIs; I showed how this tool directly affects those KPIs. It does not distract from work but removes obstacles on the way to it. That is the strongest argument.
