Seasonal product manager
Загальна інформація
Senior product manager
More than 15 years in IT Product management and software…
More than 15 years in IT Product management and software…
Послуги
Діяльність
8 тис. послідовників
-
Oleksii Goncharov поділив(ла)ся цимGrowing a product past 600K DAUs in under two months is impressive. Doing it without a free tier is a masterclass in demand. Grok Bot's trajectory right now: • Under 100K daily active users in early September • Over 600K daily active users by late October • 16 consecutive days of continuous DAU growth x.com It’s always fascinating to study how new tools break through acquisition plateaus when users have to pay from day one. https://lnkd.in/dW8mTyei https://lnkd.in/dQhFubyx #grokbot #AI #tools
-
Oleksii Goncharov зроблено репост цьогоOleksii Goncharov зроблено репост цьогоHate being interviewed by AI for a job opening? Troll it instead 😂 Or invite your own AI agent to be the interviewee. And let them discuss your passion for the company while you go make breakfast. But seriously, I don't take any company seriously that sends AI to interview people. This is the biggest hypocrisy in AI these days. I build AI sales and marketing engines for B2B companies, so I automate plenty of tasks. Yet this is the one automation I refuse to build even when clients ask me directly. If you don't have time to interview a human, don't hire one. Full stop. A company using AI to interview you might as well assign you an AI manager tomorrow. Or let AI lay you off because you're simply a cost on a spreadsheet and they need to boost profits. It's OK to automate manual tasks or complex workflows, but it's NEVER OK to put AI in charge of humans. P.S. What's your take? Would you let AI interview you or be your manager?
-
Oleksii Goncharov зроблено репост цьогоOleksii Goncharov зроблено репост цьогоWant to get into AI? NOW is the time. Stanford's 2026 AI Index puts organizational AI adoption at 88%. Generative AI reached 53% of the global population quicker than the PC or the internet ever managed. And the productivity numbers aren't vague. The report cites gains of 26% in software development, around 50% in marketing output and 14–15% in customer support. The opening is still wide open, though. Regular AI use among employees sits between 40% and 48% across North America and Europe. So the tools are everywhere, while knowing what to do with them is nowhere near universal. Closing that isn't just about picking a tool, it's about being part of what's building the next layer of them. GenAI Works is raising to keep growing the Academy, HackOS, and ToneUp, backed by $3.5M in expressed interest so far. Take a look: https://lnkd.in/dccipxb5 What's held you back from trying AI properly? 𝘐𝘯 𝘮𝘢𝘬𝘪𝘯𝘨 𝘢𝘯 𝘪𝘯𝘷𝘦𝘴𝘵𝘮𝘦𝘯𝘵 𝘥𝘦𝘤𝘪𝘴𝘪𝘰𝘯, 𝘪𝘯𝘷𝘦𝘴𝘵𝘰𝘳𝘴 𝘮𝘶𝘴𝘵 𝘳𝘦𝘭𝘺 𝘰𝘯 𝘵𝘩𝘦𝘪𝘳 𝘰𝘸𝘯 𝘦𝘹𝘢𝘮𝘪𝘯𝘢𝘵𝘪𝘰𝘯 𝘰𝘧 𝘵𝘩𝘦 𝘪𝘴𝘴𝘶𝘦𝘳 𝘢𝘯𝘥 𝘵𝘩𝘦 𝘵𝘦𝘳𝘮𝘴 𝘰𝘧 𝘵𝘩𝘦 𝘰𝘧𝘧𝘦𝘳𝘪𝘯𝘨, 𝘪𝘯𝘤𝘭𝘶𝘥𝘪𝘯𝘨 𝘵𝘩𝘦 𝘮𝘦𝘳𝘪𝘵𝘴 𝘢𝘯𝘥 𝘳𝘪𝘴𝘬𝘴 𝘪𝘯𝘷𝘰𝘭𝘷𝘦𝘥. 𝘎𝘦𝘯𝘢𝘪 𝘞𝘰𝘳𝘬𝘴, 𝘐𝘯𝘤. 𝘩𝘢𝘴 𝘧𝘪𝘭𝘦𝘥 𝘢 𝘍𝘰𝘳𝘮 𝘊 𝘸𝘪𝘵𝘩 𝘵𝘩𝘦 𝘚𝘦𝘤𝘶𝘳𝘪𝘵𝘪𝘦𝘴 𝘢𝘯𝘥 𝘌𝘹𝘤𝘩𝘢𝘯𝘨𝘦 𝘊𝘰𝘮𝘮𝘪𝘴𝘴𝘪𝘰𝘯 𝘪𝘯 𝘤𝘰𝘯𝘯𝘦𝘤𝘵𝘪𝘰𝘯 𝘸𝘪𝘵𝘩 𝘪𝘵𝘴 𝘰𝘧𝘧𝘦𝘳𝘪𝘯𝘨, 𝘢 𝘤𝘰𝘱𝘺 𝘰𝘧 𝘸𝘩𝘪𝘤𝘩 𝘮𝘢𝘺 𝘣𝘦 𝘰𝘣𝘵𝘢𝘪𝘯𝘦𝘥 𝘩𝘦𝘳𝘦: 𝘩𝘵𝘵𝘱𝘴://𝘣𝘪𝘵.𝘭𝘺/3𝘈𝘗𝘭𝘜𝘬𝘑
-
Oleksii Goncharov зроблено репост цьогоOleksii Goncharov зроблено репост цього"Product managers, no more PRDs! Build a prototype first" This hype triggered me so bad, but now I am ready to eat my words. After working on AI-powered products, I agree that we should build prototypes earlier. The hype says: PMs can vibe-code now, so why not. My reason is different: AI-powered products work differently: 👉🏻With deterministic products: If a user presses X —> we return Y. 👉🏻With AI-powered products before a prototype: A user can ask it to do 1000 things -> we have no idea what it returns 😄 So the prototype becomes a discovery tool: what can the thing do out of the box? But for the record, I still believe a problem should be defined before a prototype: Problem -> solution direction -> prototype -> final PRD. And I don’t expect to change my mind here.
-
Oleksii Goncharov поділив(ла)ся цимNice Mad Max style IA movieOleksii Goncharov поділив(ла)ся цимNailed it! Somebody just turned the race for AGI into an AI-generated Mad Max trailer 👏😂 The funniest part is when Zuck wakes up from the Metaverse to ride a llama while Jensen Huang supplies GPUs to everyone else. Scripted by Sherpa (Pocket FM's AI fiction tool), rendered by Seedance 2.5 (ByteDance's AI video model). Hits even harder given that Anthropic, OpenAI, and xAI just called for slowing frontier AI development. Absolutely brilliant. P.S. also check out How to Use GPT-6 Astra, the OpenAI Model Jensen Huang Called AGI 🤖: https://lnkd.in/dqgY-7tM
-
Oleksii Goncharov поділив(ла)ся цимThis is a great webinar.Oleksii Goncharov поділив(ла)ся цимWhat does it actually take to be a great Product Manager today? In many organizations, the Product Manager role has gradually become centered around backlog management, requirements, stakeholder coordination, and keeping delivery moving. All important things. But modern Product Management is much broader than that. Great Product Managers need to understand the customer, shape product strategy, discover and validate solutions, work effectively with engineering and design, use data to make better decisions, think about go to market, and help their teams take real ownership of outcomes. That's what we mean by being a Full Stack Product Manager. On September 9, we're running our free one hour webinar on the topic again. Drawing on our experience from working in companies ranging from startups to Spotify, iZettle and other large product organizations, we'll share our view of the skills modern Product Managers need and what the role looks like in an empowered product organization. 📅 September 9, 08:00-09:00 CEST 🎟️ Free webinar If you're a Product Manager, lead Product Managers, or are trying to develop the Product Management capability in your organization, we'd love to have you join us. Register here: https://lnkd.in/djU4erHA
-
Oleksii Goncharov поділив(ла)ся цимTotally agree! It is the biggest confusion for HR and recruiter. Those two roles were mess up too often.Oleksii Goncharov поділив(ла)ся цимIn 2026, we need to end this madness. Product Owner is not a job title. When you split the roles: - Product Manager talks to the business and customers. - Product Owner ("backlog administrator") works with developers and documents "the requirements." It's one of the worst anti-patterns in Product Management. A typical argument is that combining two roles is "too much work for a single person." That might happen if you spend days attending useless meetings or writing detailed instructions. But if you empower others, prioritize work, and focus on value without BS, things go smoothly. I agree with Marty Cagan, who wrote that to succeed as a Product Manager, you need: - Direct access to users and customers - Direct access to business stakeholders - Direct access to engineers and designer No proxies. Product Owner included. The only valid setup is that the Product Manager and Product Owner are the same person with the end-to-end responsibility. In particular, it's essential that the Product Manager, Product Designer, and at least one Engineer perform Product Discovery together. Finally, if you work in Scrum, as PSPO III, I'd like to emphasize that Product Owner is just accountability, and Product Manager is a job title. The Product Owner's accountability is best fulfilled by an experienced Product Manager. And frankly, it's August 2026. The backlog work can be fully delegated to an agent. Give it strategic context in a CLAUDE.md and it writes the stories, managed roadmaps, and asks you only when the intent is unclear. What's left is the part that was always the job: discovering what to build. Do you agree? Disagree? Let me know in the comments. --- Enjoy this? ♻️ Repost to help PMs avoid this anti-pattern. Want a hi-res PDF of this picture? 📌 Download 50+ high-res PM infographics, like this one, by subscribing here: https://lnkd.in/dkBsZ-ZY --- P.S. Want to go further and learn how to strategize and build AI products as a PM? Full accountability. 8 AI PM cohorts (Anthropic, Google, OpenAI) at the price of one. Only for my community: 👉 https://lnkd.in/dS6sgqnZ
-
Oleksii Goncharov опубліковано цеA customer tells you exactly what feature to build. That's the moment most product managers get it wrong. It feels like a gift — clear, specific, actionable. So you write it down and it goes on the roadmap. But a feature request is a guess wearing a costume. The customer isn't a product designer; they're pattern-matching from tools they already know, reaching for the nearest familiar shape instead of describing what actually happened to them. The instinct to fix is to ask "would you use this if we built it?" That question is almost useless — everyone says yes to a hypothetical. Ask about the past instead: "Tell me about the last time you tried to do that. What happened next?" I've watched this play out the same way more than once. A customer says "add drag-and-drop scheduling." A junior PM writes it down as-is. A senior PM asks about the last time the customer had to reschedule the team — and learns the real problem was three open tabs and no visibility into who was free. Drag-and-drop wouldn't have touched that. Visibility would have. The discipline is staying in the customer's past behavior, not their future feature wishlist. Two phrases do most of the work: "Tell me more about that." And: "What happened next?" Domain experts are the worst at this — the more you know the product, the harder it is to resist finishing the customer's sentence with your own solution. Next customer call, count how many times you catch yourself about to suggest a feature instead of asking what happened. #ProductManagement #CustomerDiscovery #JTBD #UserResearch
-
Oleksii Goncharov опубліковано цеEvery remote professional eventually has to say "no" to someone they can't read the body language of. Over a screen, "no" lands ten times harder than it does in a room. How to say "no" and stay in good relations? I've learned there's a better move than yes, and a better move than a flat no. Saying yes to everything asked of you is how your role, your product, or your project quietly turns into an unmaintainable mess nobody's proud of. Saying no flatly protects your focus but burns trust — especially remotely, where a blunt decline reads as dismissal, not diligence. The actual skill is neither. It's turning the request into a question: "Walk me through what happens when you hit this. What are you doing about it today?" I watched this play out with a request for custom data tagging in a shared workspace. Instead of building it, the response was: "Who on your team will own naming and auditing these tags? What happens when someone creates a duplicate?" The requester paused, then said, "Actually, that sounds like a mess. Maybe we just need a few dropdown options." They rejected their own idea — because the questions surfaced the real cost, not because anyone told them no. The request is never the point. It's a symptom. Every "no" you deliver should leave the other person having learned something about their own problem, not just about your limits. Next time you're about to decline something over Slack or email, try asking one operational question before you answer at all. #RemoteWork #ProductManagement #StakeholderManagement #WorkingRemotely
Oleksii Goncharov коментує допис
1день
Supabase is a good example of a great product for AI era of development which is both good for agents and for human with it's UX and easy to use approach. Thanks for your work, guys! Paul Copplestone
-
Oleksii Goncharov сподобалося цеOleksii Goncharov сподобалося цеSupabase (YC S20) has become one of the default backends for the AI coding era. The open source Postgres platform now has 13 million users, spins up more than a million databases every week, and roughly 70% of its new activity is coming from agents. As coding shifts from developers writing software by hand to agents building on their behalf, Supabase has been rebuilding itself around that new user. In this episode of The Lightcone, Supabase co-founder and CEO Paul Copplestone joins Garry, Harj, and Jared to talk about what happens when everyone can become a builder. They dive into why personal software may become as common as personal documents, how to design products that agents actually want to use, and why knowing what to build may matter more than knowing how to build it. https://lnkd.in/gMz5hucp
-
Oleksii Goncharov сподобалося цеOleksii Goncharov сподобалося цеGrok for self-improving agentic marketing 4 Grok loops, 8 steps each, for ads and SEO 👇 1/ Model the money first Google Ads Grok starts with margin, LTV and break-even ROAS. Every later call is judged against that number. 2/ Mine search terms, not keywords It clusters queries by n-gram and sculpts negatives from proven winners. Waste shows up by theme, not one term at a time. 3/ Build a creative matrix on Meta Meta Grok maps angles to awareness, then tests angle, hook and format in a sandbox. Winners graduate to Advantage+. 4/ Kill on leading metrics Hook rate, hold rate and CTR decide before ROAS does. Budgets grow up to 20% a day, so learning never resets. 5/ Start SEO with revenue pages SEO Grok maps the URLs that make money, then crawls logs and clusters demand. Technical debt gets paid down before new content. 6/ Fix wrong AI answers at the source GEO Grok benchmarks share of voice on a fixed prompt set and traces the pages models trust. Then it publishes pages worth citing. 7/ Keep, roll back, learn Every loop runs holdouts against a control. Winners become rules for the next loop. The step most teams skip is measuring against a control.
-
Oleksii Goncharov сподобалося цеOleksii Goncharov сподобалося це32 Claude skills that take product strategy off your plate. Sharing the free guide 👇 1/ Diagnose Strategic question frame, product health read, issue tree, hypothesis board. You know which decision the strategy feeds before the data piles up. 2/ Know the market and the customer Competitive analysis, needs-based segmentation, opportunity solution tree, market sizing, Lean Canvas. Every figure names its source or is marked as an assumption. 3/ Choose Product vision board, strategic options, decision matrix, strategic bets, not-doing list. Each bet says what would prove it wrong, and the not-doing list is written down. 4/ Stress-test Scenario planning, red team review, pre-mortem, recommendation memo. Someone argues with the plan before a quarter is committed to it. 5/ Put numbers on it Business case, north star metric. Finance gets a return with its assumptions shown, not a guess. 6/ Measure and roadmap Strategy KPIs, impact map, now-next-later roadmap, quarterly OKRs. The roadmap stops being a feature list the board reads as promises. 7/ Tell it Product strategy document, one-page strategy, product strategy deck, roadmap review deck. Teams can repeat the strategy and say no against it. 8/ Report and review Board memo, strategy decision record, quarterly strategy review, strategy change note. Claude drafts; a named person makes every strategic choice. Free access 👇
-
Oleksii Goncharov сподобалося цеGrowing a product past 600K DAUs in under two months is impressive. Doing it without a free tier is a masterclass in demand. Grok Bot's trajectory right now: • Under 100K daily active users in early September • Over 600K daily active users by late October • 16 consecutive days of continuous DAU growth x.com It’s always fascinating to study how new tools break through acquisition plateaus when users have to pay from day one. https://lnkd.in/dW8mTyei https://lnkd.in/dQhFubyx #grokbot #AI #tools
Досвід та освіта
Мови
-
English
Повний професійний рівень володіння
-
Russian
Рідна мова або володіння двома мовами
-
Ukrainian
Рідна мова або володіння двома мовами
Отримані рекомендації
11 людей рекомендують Oleksii
Приєднайтеся зараз, щоб переглянути