Contents:

Free Python course ➞ Mini-course for For beginners and experienced coders. Four cool projects in the portfolio, live communication with the speaker. Click and find out what you can learn in the course.
Learn moreStepan Velichko is a renowned figure in his field, possessing significant experience and knowledge. His work covers a wide range of aspects, making him an expert in various fields. Stepan actively shares his views and ideas, which contributes to the development of the professional community. His achievements and contributions to the industry deserve attention and respect. Thanks to his experience, Stepan Velichko has become an authority whose opinion is listened to by many.

About the expert
Our expert has deep knowledge and significant experience in his field. He regularly shares his knowledge through articles, webinars and consultations, helping people understand complex issues. Thanks to his years of experience and professional approach, this expert has earned the trust of clients and colleagues. His goals are to provide relevant information and practical recommendations to help you achieve your goals. With his help, you can make informed decisions and develop your skills.
Stepan Velichko is a product manager at Cian, responsible for the development and optimization of the long-term rental service "Sday/Snimi." His work is focused on creating a user-friendly platform that simplifies the housing rental process, providing users with access to up-to-date offers and effective search tools. The service "Sday/Snimi" is focused on meeting the needs of tenants and landlords, offering an intuitive interface and a wide selection of properties.
Links are an important element of web content, as they help users navigate websites and find the information they need. In SEO optimization, links play a key role, as they influence page rankings in search engines. Internal links improve the site structure and contribute to user retention, while external links can increase the authority of a resource. Effective use of links improves page indexing and search engine visibility. Furthermore, it's important to monitor link quality and relevance to ensure maximum benefit for both users and SEO. Link optimization is an integral part of a successful website promotion strategy. "Sday/Snimy" is an innovative startup within Cian that simplifies the process of renting and finding long-term rental housing in Russia. Our team consists of 8 experienced developers who are actively testing various hypotheses, researching market niches, and experimenting with the design of our service. We strive to create a user-friendly platform that meets user needs and ensures effective interaction between landlords and tenants.
We changed the usual workflow to effectively manage tasks without hindering the development and creativity of developers.
Involved the team in the processes
Previously, responsibility for hypotheses in the team lay with the product manager. They would seclude themselves in an isolated space to generate ideas and then present them to the team. However, over time, it became clear that this approach was ineffective. Teamwork and joint discussion of hypotheses allow us to identify more valuable ideas and avoid one-sided thinking. Joint hypothesis generation promotes a deeper understanding of user problems and needs, and allows us to take into account different points of view, which ultimately leads to higher-quality solutions.
We began to involve all team members in the hypothesis development process. This approach allowed us to use a diversity of opinions and ideas, which significantly enriched our creative process. Each team member contributed, which facilitated deeper analysis and the search for effective solutions. This allowed us to generate higher-quality hypotheses based on collective experience and knowledge. This approach not only improved the final result but also fostered team cohesion and increased motivation.
The first step was a deep dive into the product. We clearly articulated goals for the next 3-6 months and explained their origins. This allowed everyone involved in the project to understand exactly what they were doing and why it was important.
In the second stage, we regularly monitored goal achievement. During demos and retrospectives, we assessed results using metrics and drew corresponding conclusions. This allowed everyone on the team to see the current state and direction, which contributed to increased transparency and efficiency.
The first two steps yielded significant results. The team began to pay more attention to new ideas, analyze them, and align them with our goals, rather than simply completing assigned tasks. If someone noticed any shortcomings in the project, they not only expressed their opinions but also suggested possible solutions. This created an atmosphere of openness and collaboration, which contributed to improving the quality of work and achieving shared goals.
We created a common channel for exchanging ideas so that everyone could freely propose new solutions and discuss the product. An additional channel, "Sdi-Snim-Pogoli," was added to Slack, where participants can share their findings, whether a new solution, an interesting service, or an informative article. This creates an atmosphere of constant brainstorming. Initially, the channel was intended only for the "Sdi-Snim" team, but after Cian learned about it, employees from other teams began joining. This approach promotes active knowledge sharing and the creation of innovative ideas, which in turn has a positive impact on product development.
As a result, the number of ideas has increased significantly. Now suggestions come not only from product managers, but also from developers, designers, and employees from other teams. This diversity of opinions and approaches contributes to more creative solutions and improves the overall development process.
We tried different methodologies and adapted them to our format
We use Agile, adapting it to our unique needs. Although we formally set weekly sprints, in practice we rarely stick to them. Processes change so frequently that they need to be constantly adjusted to current tasks. Recently, we switched to a mixed methodology, which is more in line with the principles of Kanban. This allows us to respond more flexibly to changes and manage projects effectively.
Previously, our team was simultaneously working on more than ten projects, all of which were cross-stack. This made it difficult to distribute tasks among participants, and each person could work on up to four projects at a time. This approach often led to chaos and inconsistency within the team. As a result, we implemented limits on the number of tasks in progress. Now, no more than three projects can be in progress, and we don't take on new ones until at least one is completed. A project is defined as a separate piece of functionality or feature. This measure improves team efficiency and enhances the quality of task completion. Dynamic rental price adjustments are an effective tool that allows owners to optimize their offerings. Owners can set their desired price, and our service automatically adjusts it based on demand. If interest in an ad is low and the number of calls drops, the price is reduced by 5%. If numerous inquiries are received on the first day, for example, 100 calls, the price may be increased. A graph is available in the owner's personal account, visualizing the relationship between price and response rate. This helps clients objectively assess the market value of their apartment and adapt it to current market conditions.
Initially, we held traditional Agile retrospectives every week, analyzing the results of the sprint. However, we soon realized that this format wasn't suitable for our team. The developers were focused on their own projects and didn't want to raise issues in general discussions. As a result, we changed our approach and began holding project-specific retrospectives. Now, after the completion of each project, we meet with key developers and all team members. During these meetings, we discuss any issues that have arisen, formulate specific actions, and assign responsibility for their implementation. We share the results of these meetings with the rest of the team, which helps improve the process and increase work efficiency.
For each project, we form a mini-team.
The first step is to assign a responsible developer who will manage the project. Their responsibilities include informing the tech lead and product manager about any issues that have arisen and resolving them. A responsible developer handles both small tasks, such as updating Jira issue statuses, and more complex issues related to new technical requirements. They also coordinate the activities of all team members, ensuring effective communication and completion of assigned tasks.
The team composition is determined by the specifics of the project and its tasks. Some projects are focused solely on the backend or frontend, as well as tasks that require collaboration between backend and frontend developers. The team must be balanced and include specialists who can effectively collaborate to achieve the overall project goals.
We regularly generate new ideas, making it impossible to compile a final list of projects for the upcoming quarter and hold traditional meetings to evaluate them. Developers and managers exchange ideas in a common channel and then jointly determine which ones will most effectively help achieve key metrics. However, the question of the necessary time and financial costs for the implementation of these projects remains open.
Currently, specialists from various fields regularly gather for meetings where product managers present concepts for future features. Experts select one project, conduct a preliminary assessment, and exchange opinions with other participants. As a result, the backlog of ideas is filled with valuable data, which allows for more effective planning and implementation of new features. This approach not only improves the quality of decisions but also contributes to the creation of more successful products that meet user requirements.
- We understand which stacks are needed to implement the projects;
- We receive an approximate cost estimate from other stacks;
- We build a preliminary project architecture.
Based on this data, we can optimally allocate team resources. For example, we know that next week mobile developers will be free for three days. By reviewing the backlog, we can identify features that will have a positive impact on our metrics and select those that will take no more than three days to implement. This will allow us to use our developers' time efficiently and increase team productivity.
Development has begun to be encouraged
Developers of the Sdai/Snimi platform have unique opportunities for career growth both horizontally and vertically. The company offers a variety of tasks that allow them not only to improve their technical skills but also to develop their team management skills, which opens the way to a team lead position. This approach to career development helps create a professional environment in which every employee can realize their potential and make a significant contribution to the company's success.
Currently, three developers have reached their career ceilings in their positions. Two of them are striving to become team leads, while the third has chosen to focus on the role of expert. He is more interested in solving complex technical problems than in managing a team. This division of roles highlights the diversity of career paths in IT and the importance of choosing a direction that aligns with personal interests and professional goals.
We prefer not to work on hypotheses for longer than two to three weeks. We typically develop small features or break them down into smaller tasks so we can quickly launch, test, and make changes if necessary. This gives us flexibility, but also creates certain challenges. A shortage of specialists with multiple projects requiring the attention of a single person complicates the process. To avoid development delays, we had to carefully coordinate the work schedule and manage the interdependencies between projects.
Our Python developer faced a task in C# when there were no available specialists in this field. To avoid wasting time waiting for help, he learned the necessary aspects himself and wrote the code in C#. Over time, he began to take on more C#-related tasks. Later, a similar situation arose in mobile development. Although these tasks seemed simple to experienced developers, their solution significantly accelerated the development process and increased the team's efficiency.

Mobile developers have become unbearably dependent on the backend, completing tasks with mocks and waiting for a suitable API to appear. Even if the mocks worked successfully, the backend might implement methods slightly differently, leading to project failures. As a result, the developers began gradually mastering the backend to improve the interaction between the frontend and the server. This decision allowed them to solve problems more efficiently and minimize the risks associated with a discrepancy between the expected and actual API functionality.
In our team of eight, only two are unfamiliar with other technologies. The main Pythonista, who started it all, has already mastered C#, JavaScript, and is even developing features for iOS. The remaining developers have a primary stack and one additional one. Now the team is able to solve small problems in various languages, which eliminates dependence on a single specialist and significantly increases flexibility in project work.
We formed two independent teams to test hypotheses.
Product managers are often involved in strategic projects that take a significant amount of time, sometimes up to a month. As a result, they lack time to conduct quick experiments. However, testing small features, such as a new button design, a banner change, or optimized headlines, is an important part of the product improvement process and should be conducted regularly. This allows us to identify user preferences and improve the effectiveness of interactions with the product.
We were already collaborating with a mid-level C# developer with management skills. He demonstrated an interest in organizing processes and collecting feedback, which allowed him to quickly adapt to the team and begin generating ideas. Over time, he took the initiative to conduct retrospective meetings and implemented a regular process for assessing the status of team members. This positively impacted work efficiency and the team atmosphere.
The first developer on the team reached the fullstack level. In light of this, we decided to create a growth team that will test several hypotheses per week using minimum viable products and track key metrics. The team included a product lead with a mid-level C# skill level, a fullstack developer, and an analyst with a part-time researcher. This will allow us to conduct experiments more effectively and improve results.
The product lead performs many key tasks, including managing product strategy, team coordination, and stakeholder engagement. They are responsible for defining the product vision, its development, and implementation, as well as analyzing the market and user needs. The product lead's primary goal is to create value for customers and achieve the company's business goals. Another important task is monitoring and evaluating product performance, which allows for timely implementation of necessary changes and improvements. A successful product lead provides a link between different teams, which facilitates effective collaboration and accelerates the development process.
- sets up processes;
- organizes brainstorms;
- prioritizes hypotheses;
- is responsible for metrics;
- monitors team performance.
The analyst spends approximately 8 hours a week brainstorming, prioritizing tasks, and analyzing hypotheses, while the researcher ensures the transfer of user feedback. These processes are critical to understanding user needs and optimizing products. Effective communication between the analyst and the researcher contributes to improved decision-making and higher customer satisfaction.
Before the start of the sprint, the product manager identifies the key metric that the team should focus on. During the brainstorming, participants propose various hypotheses. Each idea is then presented to the rest of the team for discussion and criticism. Following this, the most viable proposals are prioritized based on three key criteria: potential impact on metrics, feasibility, and alignment with the project's strategic goals. This approach allows the team to effectively allocate resources and focus on the most promising initiatives. Belief in success is key to achieving goals. This confidence helps overcome obstacles and move forward despite difficulties. People who believe in their success are able to maintain motivation and focus on their ambitions. Belief in oneself and one's abilities fosters a positive mindset and confidence in decision-making. This is an important aspect in both personal and professional life, as it supports the desire for development and achievement. By strengthening belief in success, we create the foundation for future victories. Banner advertising can be effective, but its impact on a startup's goals can be limited. For example, this format may attract only 0.1% of the target audience. It's important to analyze the effectiveness of advertising campaigns and their ability to achieve goals in order to optimize marketing strategies and increase conversion.
Complexity is an important aspect to consider across various areas. It can range from simple tasks to more complex and multifaceted issues. Understanding the level of complexity helps not only in work planning but also in determining the required resources and time to complete tasks. Taking complexity into account can also optimize processes and increase efficiency. Developing strategies aimed at simplifying complex tasks can lead to significantly improved results. It's important to remember that properly assessing complexity contributes to more effective project and resource management.
Hypotheses are passed on to a full-stack developer for implementation and testing.
The team currently tests four hypotheses each week, spending less than 8 hours of development on each. This allows for the efficient evaluation of ideas and the rapid implementation of successful solutions.
The product lead will likely move from C# to the product area in the future. On the growth team, he gains practical experience, rather than being limited to theory from articles and books. This opens up opportunities for further development and a potential promotion to a product manager position on our team.
At the beginning of the quarter, we set goals and then hold weekly meetings to discuss the team's growth areas. An important task for the product lead is to develop the necessary skills and improve processes. If the number of hypotheses to prioritize is lower than expected, they look for ways to increase their number. We also explore topics they haven't yet encountered but would like to explore, such as analytics. In this way, we strive for continuous development and improvement of the team's work.
Within the team, employees have the opportunity to delve deeper into related areas as they wish. For example, a user experience researcher interested in analytics receives support from a current analyst. The analyst helps them master Google Analytics and learn how to extract data using SQL. This interaction not only develops individual skills but also improves the team's overall effectiveness. The ability to share knowledge and experience within the team plays a significant role in employee professional growth and improving the quality of work.
After the successful launch of the growth team and its autonomous operation, we decided to create a new team.
Successful scaling of the service requires constant experimentation with offerings, including text, visual elements, and mechanics. When users experience banner blindness and automatically skip ads, the online sales process becomes more complex. New sales mechanics often fall outside the growth team's expertise, and the process of developing and testing hypotheses requires about a week for each. Therefore, it is important to implement innovative approaches and optimize existing strategies to increase sales efficiency and improve interaction with the audience.

One of our developers, having reached the senior level, expressed a desire to move to the team lead position. However, in a team of eight, not everyone can fill this role. This creates certain challenges for career advancement and requires a careful approach to the development of each team member. It is important to find a balance between the employees' ambitions and the company's capabilities to ensure the team's effectiveness.
He was invited to lead the offer development team. The main task was to establish processes for launching and testing all N hypotheses within the established deadlines. As a result, the developer improved his management skills, and the team was able to effectively test hypotheses related to sales mechanisms. This allowed them to optimize their approach to creating offers and increase their effectiveness in the market.
In addition to the team lead, the team includes a designer, a copywriter, and a frontend developer. Like the growth team, they organize processes without the involvement of a product manager and handle the full cycle of tasks. These specialists work closely together, ensuring the effective implementation of projects and the achievement of goals. Each of them makes a unique contribution, which helps to create a high-quality product and improve the user experience.
- brainstorm offer ideas;
- develop designs;
- conduct collective design reviews;
- launch offers;
- conduct post-launch analytics.
The developer develops team lead skills, learning how to effectively organize a team, deliver projects on time, and optimize work processes. He is passionate about problem solving, has built strong relationships with colleagues, and demonstrates high results in achieving goals.
Bonus: what to read if you want to move from development to product or management
One of the key qualities of a successful product manager is good visibility. Analysis of various cases and examples from practice becomes an important tool for development in this area. Early in my career, I had limited information sources and had to glean knowledge bit by bit. Today, the internet offers a wealth of materials in Russian, which significantly simplifies the learning process and helps develop essential skills more quickly. Regularly studying successful case studies allows for a better understanding of the market, user needs, and current trends, which in turn contributes to the creation of a high-quality product. Blogs are one of the most effective sources of case studies and training materials for product management professionals. They allow you to stay abreast of the latest trends in marketing and business thanks to regularly updated information. Reading blogs helps you gain new knowledge and apply it in practice, which contributes to professional growth and increased competitiveness.
- GoPractice not only provides product management theory and analyzes case studies, but even offers a simulator for immersing yourself in product management.
- Epic Growth has entire series on IT product development and a channel with free content.
- Ivan Zamesin and Ilya Krasinsky, practicing experts and mentors, generously share their experience and answer questions about product management in their blogs.
- The Growth.Design resource provides a detailed analysis of user flows from various products and provides links to scientific articles.
- The Yandex Academy YouTube channel has a playlist called "School of Management."
Books provide the fundamental knowledge necessary for understanding the mechanisms and reasons behind the functioning of various processes. Reading books promotes deep understanding by developing analytical thinking and making informed decisions.
- Lean Startup is a basic theory of startup management. I recommend starting with it.
- "Ask Mom: How to Communicate with Clients and Validate Your Business Idea When Everyone Around You is Lying?" - How and Why to Conduct User Research.
- "When Coffee and Cabbage Are Competitors" - a book about user research and the Jobs To Be Done approach.
Once you've mastered the basics, the question "What to learn next?" will become irrelevant. As you delve deeper into the topic, you'll be able to better define your interests and discover many new resources. It's recommended to study theory through books, follow experts in your field, and learn from others' experiences. This will help you significantly speed up the learning process and develop skills in your chosen field.

