<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Max Antonov on Medium]]></title>
        <description><![CDATA[Stories by Max Antonov on Medium]]></description>
        <link>https://medium.com/@mantonov?source=rss-d151506cc83f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*KAcjBPBusesMnQGu-VvxcQ.png</url>
            <title>Stories by Max Antonov on Medium</title>
            <link>https://medium.com/@mantonov?source=rss-d151506cc83f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 20:04:34 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mantonov/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Is strategy supposed to be difficult to understand?]]></title>
            <link>https://mantonov.medium.com/is-strategy-supposed-to-be-difficult-to-understand-0c78b84a57e3?source=rss-d151506cc83f------2</link>
            <guid isPermaLink="false">https://medium.com/p/0c78b84a57e3</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[strategic-thinking]]></category>
            <category><![CDATA[product-leadership]]></category>
            <category><![CDATA[strategy]]></category>
            <dc:creator><![CDATA[Max Antonov]]></dc:creator>
            <pubDate>Mon, 07 Apr 2025 10:47:42 GMT</pubDate>
            <atom:updated>2025-04-07T10:47:42.963Z</atom:updated>
            <content:encoded><![CDATA[<p>Bad strategy documents aren’t your fault.</p><p>You join a new team. You’re handed a 30-pager full of buzzwords, abstract goals and empty phrases. You read it. You reread it. Still lost.</p><p>It feels like you’re the problem. You’re not. The document is.</p><p>Most strategy docs aren’t written to be understood. They’re written to impress. Or to tick a box. They sprawl with vague visions and empty frameworks, then expect alignment to magically follow.</p><p>But the job of a strategy isn’t to sound smart.</p><p><strong>The job of a strategy is to create clarity. Direction. Focus. And what to ignore.</strong></p><p>A good strategy is short and sharp. Like a pitch. You should be able to explain it in 30 seconds. Use <a href="https://antonov.com.au/scqa-framework">SCQA</a> if you need help: Situation, Complication, Question, Answer.</p><p>If you’re a Product Manager, that’s your job. Not just writing the doc. Shaping the strategy. Testing it. Pressure-proofing it with your team and execs.</p><p>So if you’re staring at a bloated, broken strategy, don’t wait for permission.</p><p>Tear it apart. Make it clearer. Make it tighter. Make it usable.</p><p>Alignment doesn’t come from reading. It comes from understanding.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0c78b84a57e3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product-market fit doesn’t exist]]></title>
            <link>https://mantonov.medium.com/product-market-fit-doesnt-exist-40923986884f?source=rss-d151506cc83f------2</link>
            <guid isPermaLink="false">https://medium.com/p/40923986884f</guid>
            <category><![CDATA[product-market-fit]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-marketing]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product]]></category>
            <dc:creator><![CDATA[Max Antonov]]></dc:creator>
            <pubDate>Thu, 03 Apr 2025 05:42:46 GMT</pubDate>
            <atom:updated>2025-04-03T05:42:46.092Z</atom:updated>
            <content:encoded><![CDATA[<p>It’s a myth we tell ourselves to feel like we’re on the right track.</p><p>“Agile” suffered the same fate (<em>at least there’s the agile manifesto that exists</em>). Started as a working philosophy, ended up a bingo word. Everyone says they have PMF. No one can show you where it lives. They just point to a vibe. Some traction. A few good months. A round that closed fast.</p><p>“We’ve got it!” Based on what? Revenue? Retention? NPS? Survey? Gut feeling?</p><p>The phrase has become a catch-all. Founders claim it when growth feels easier than usual. Investors expect it before writing a cheque. But there’s no standard. No scoreboard. Every product is different. Every market reacts in its own way. What looks like PMF for one company might be a dead end for another.</p><p>Product-market fit isn’t something you find. It’s something you feel.</p><p>And sometimes, you just hope you’re right.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=40923986884f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mistakes teach faster than manuals]]></title>
            <link>https://mantonov.medium.com/mistakes-teach-faster-than-manuals-c87d49c479b9?source=rss-d151506cc83f------2</link>
            <guid isPermaLink="false">https://medium.com/p/c87d49c479b9</guid>
            <dc:creator><![CDATA[Max Antonov]]></dc:creator>
            <pubDate>Sun, 30 Mar 2025 05:08:03 GMT</pubDate>
            <atom:updated>2025-03-30T05:08:03.248Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/922/1*FBWbM_fXbUeI0EuIkIeFLQ.png" /></figure><p>Mistakes teach faster than manuals. But only if they’re visible. And shared before they sit quietly and start to build up.</p><p>When a leader owns a mistake in front of their team, something powerful happens. The room relaxes. People stop pretending everything is perfect. They stop tiptoeing. It sends a message that trying, failing and learning is part of the job — not a threat to it.</p><p>Most teams don’t freeze from lack of skill. They freeze from fear. Fear of saying the wrong thing. Fear of trying something new. Fear of being the only one who didn’t get it right. But when a leader steps up and says, “Here’s what I got wrong, here’s what I learned and here’s what I’m changing,” that fear starts to fade.</p><p>Because the next time something goes sideways, there’s no hiding. You’ve already shown how it’s done — how to take ownership, how to bounce back.</p><p>But don’t overdo it. This isn’t about dumping your insecurities on your team or confessing every minor wobble. It’s not a therapy session. Oversharing makes people uneasy.</p><p>So keep it simple. Share what’s useful. Wrap it in action. Frame the mistake as a lesson, not a spiral. Make it clear you’re learning faster than before — and pulling the team forward with you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c87d49c479b9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[You can’t validate a product with opinions.]]></title>
            <link>https://mantonov.medium.com/you-cant-validate-a-product-with-opinions-a38b0a45d7f0?source=rss-d151506cc83f------2</link>
            <guid isPermaLink="false">https://medium.com/p/a38b0a45d7f0</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[validation]]></category>
            <dc:creator><![CDATA[Max Antonov]]></dc:creator>
            <pubDate>Tue, 25 Mar 2025 09:34:21 GMT</pubDate>
            <atom:updated>2025-03-25T09:34:21.690Z</atom:updated>
            <content:encoded><![CDATA[<h3>Validation Comes After Launch</h3><p>You can’t validate a product with opinions.</p><p>People love to be nice. They’ll tell you what you want to hear. “I’d buy that.” “Sounds awesome.” “I’d totally use it.” They’re not lying to be cruel. They’re trying to be supportive. But support doesn’t equal commitment.</p><p>The second you ask for money, everything changes.</p><p>That’s the gap most early teams fall into. They build confidence through conversation, then get blindsided when no one converts. The truth? Feedback is cheap. Intent is slippery. Until someone clicks buy now, you’ve got nothing but noise.</p><p>This is why validation through interviews alone is a trap. You walk away with quotes and warm fuzzies, but no proof. No one wants to crush your idea to your face. No one wants to admit they’d never use it. So they hedge. They smile. They say “maybe.” You hear “yes.”</p><p>Only the market tells the truth.</p><p>Put something live. Doesn’t need to be finished. Doesn’t need to be perfect. Just needs to be real. Real enough for people to understand it, want it, and act. Even if that action is signing up. Giving an email. Pre-ordering. Paying a deposit.</p><p>You’re not looking for compliments. You’re looking for behaviour.</p><p>If people really want what you’ve made, they’ll show you. They’ll take out their wallet. They’ll share it with friends. They’ll come back again. That’s real validation. Not the stuff they say. The stuff they do.</p><p>That’s why speed matters. The faster you get to market, the faster you find out if your idea has legs. You don’t need a big launch. You don’t need a press release. You need a link you can send to five people who might actually care. Then watch what they do.</p><p>Listen. Adjust. Ship again. It’s not about nailing it the first time. It’s about learning fast enough to survive.</p><p>So don’t wait. Don’t hide behind research. Don’t collect 100 “yes” answers you can’t cash in. Put something out there. See what sticks. Move fast.</p><p>The market won’t lie. That’s the only feedback worth listening to.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a38b0a45d7f0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[This is such a great example of how important written communication is.]]></title>
            <link>https://mantonov.medium.com/this-is-such-a-great-example-of-how-important-written-communication-is-73edac739a33?source=rss-d151506cc83f------2</link>
            <guid isPermaLink="false">https://medium.com/p/73edac739a33</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[communication]]></category>
            <dc:creator><![CDATA[Max Antonov]]></dc:creator>
            <pubDate>Sun, 23 Mar 2025 06:09:04 GMT</pubDate>
            <atom:updated>2025-03-23T06:09:04.463Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xk86EEwq44PaljTnyArfWA.png" /><figcaption>c</figcaption></figure><p>This is such a great example of how important written communication is. Misalignment happens all the time — on the problems, the solutions, the details and even the language we use. So, as soon as you sense there’s misalignment and nothing is written down, the best move is to put it into words.</p><p>At least this way, you’re making your position clear.Invite others to review, comment and challenge your perspective.Get everyone on the same page before moving forward.If you don’t, that misalignment will come back to bite you later. The cost will be much higher.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=73edac739a33" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[New Year, Who Dis?]]></title>
            <link>https://mantonov.medium.com/new-year-who-dis-c964bdcdcd76?source=rss-d151506cc83f------2</link>
            <guid isPermaLink="false">https://medium.com/p/c964bdcdcd76</guid>
            <dc:creator><![CDATA[Max Antonov]]></dc:creator>
            <pubDate>Mon, 06 Jan 2025 09:42:26 GMT</pubDate>
            <atom:updated>2025-01-06T09:42:26.093Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tidTkTHQUAYG981yGuppHw.jpeg" /></figure><p>Everyone talks about ‘hitting the ground running’ after the Christmas break.</p><p>Let’s be honest, no one feels like sprinting straight away at this time of the year.</p><p>Some are still catching up on sleep, recovering from all the desserts they’ve eaten, wrapping their heads around what day it is and trying not to fail one of their New Year’s resolutions in the first week of the year.</p><p>Forcing yourself into work mode overnight is hard.</p><p>I’d rather ease into it. Spend the first day reconnecting with your team, archiving all the emails from last year and marking all Slack messages as read. Oh, that feels great.</p><p>By the second day, you’re already feeling more in control.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c964bdcdcd76" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product-Led Growth vs. Sales-Led Growth]]></title>
            <link>https://mantonov.medium.com/product-led-growth-vs-sales-led-growth-4cf287410926?source=rss-d151506cc83f------2</link>
            <guid isPermaLink="false">https://medium.com/p/4cf287410926</guid>
            <category><![CDATA[product-led-growth]]></category>
            <category><![CDATA[slg]]></category>
            <category><![CDATA[sales-led-growth]]></category>
            <category><![CDATA[customer-led-growth]]></category>
            <category><![CDATA[plg]]></category>
            <dc:creator><![CDATA[Max Antonov]]></dc:creator>
            <pubDate>Tue, 09 Jul 2024 22:56:39 GMT</pubDate>
            <atom:updated>2024-07-09T22:56:39.245Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lnTnKHAID9ihZJdc8j-7mA.png" /></figure><p>I spoke to someone about sales-led vs. product-led organisations today. I used to be in the product-led camp, but not anymore. Today, I think differently. As with anything in the world, it’s not that simple — the choice depends on the context.</p><p>Sometimes you need to be tactical and assist sales in closing deals to ‘buy some time’ for continuing execution on product strategy and pushing innovation forward. If you overindex on product-led too much, you might run out of funding.</p><p>At the same time, you don’t want to onboard potential customers who don’t have the problem you’re solving or who don’t find your solution to their most important problems. Over-indexing on the sales-led approach can lead to creating a ‘Frankenstein’ product that tries to suit everyone but ends up working for no one.</p><p>The reality is that even if you have the most amazing and well-communicated <a href="https://antonov.com.au/the-purpose-of-a-strategy">strategy</a> ( <em>Are you using </em><a href="https://antonov.com.au/scqa-framework"><em>SCQA</em></a><em>?</em>) in place, there will be times when a tactical decision to onboard a new customer will happen.</p><p>So, what’s the solution? A balance.</p><p>It’s hard to quantify and put on paper because it really depends on the market, its state, business goals, product performance and maturity, and the state of your technology.</p><p>Here are a couple of things to consider when making a particular choice:</p><h3>Product-Led <strong>Pros</strong></h3><ul><li>Focus on long-term product strategy and innovation.</li><li>Encourages innovation and quality.</li><li>Enhances customer experience through well-designed products.</li><li>Differentiates through superior product offerings.</li></ul><h3>Sales-Led Pros</h3><ul><li>Helps to close deals quickly, ensuring immediate cash flow.</li><li>Direct feedback from customers influences product development.</li><li>Easier to demonstrate ROI to investors.</li><li>Adapts quickly to market changes and customer needs.</li><li>Strong immediate revenue generation.</li></ul><h3>Product-Led <strong>Cons</strong></h3><ul><li>Risk of running out of funding if not enough immediate sales.</li><li>Slower revenue growth initially.</li><li>Potential disconnect with market demands.</li><li>Longer time to market.</li><li>Higher upfront costs for development.</li></ul><h3>Sales-Led Cons</h3><ul><li>Risk of creating a ‘Frankenstein’ product that tries to suit everyone but works for no one.</li><li>Can lead to short-term thinking and reactive development.</li><li>Potential for higher customer churn if product lacks focus.</li><li>Sales-driven roadmap may overlook innovative opportunities.</li></ul><p><em>Originally published at </em><a href="https://antonov.com.au/product-led-growth-vs-sales-led-growth"><em>https://antonov.com.au</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4cf287410926" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Role Overlap Between PM and PD]]></title>
            <link>https://mantonov.medium.com/the-role-overlap-between-pm-and-pd-099c11795487?source=rss-d151506cc83f------2</link>
            <guid isPermaLink="false">https://medium.com/p/099c11795487</guid>
            <category><![CDATA[product-manager]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-designer]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Max Antonov]]></dc:creator>
            <pubDate>Sun, 07 Jul 2024 22:51:30 GMT</pubDate>
            <atom:updated>2024-07-07T22:51:30.485Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mFzMgJmD7AblSyuWKnjpXQ.png" /><figcaption>The Role Overlap Between Product Managers and Product Designers</figcaption></figure><p>Roles in product and design teams often overlap. Both <strong>product managers</strong> and <strong>product designers</strong> talk to customers, come up with feature ideas, and suggest UX improvements.</p><p>However, these overlaps can sometimes lead to conflict and frustration.</p><p>The solution is quite simple.</p><p>If you’re a product manager and your product designer is doing a great job, take a step back. There are plenty of other things you can do without getting in each other’s way — review and update your product strategy, improve collaboration with other departments, or even write a blog post. These are all good options!</p><p>If you are a product designer and the product manager is taking over your responsibilities, communicate openly about the overlap and seek a balance in responsibilities.</p><p><strong>When Should Product Managers Step In?</strong></p><ul><li>When your Product Designer asks for help.</li><li>When you need to accelerate research and interviews.</li><li>When the quality of the Product Designer’s work does not meet the required standards. In this case, provide constructive feedback and then step back.</li></ul><p>While clear roles are important, so is fostering a culture of flexibility where team members can contribute beyond their defined responsibilities.</p><p>Push for open communication and occasional role fluidity to maintain creativity and innovation.</p><p>Also, checkout out “ <a href="https://antonov.com.au/3-tips-for-better-teamwork">3 Quick Tips for Better Teamwork</a>”.</p><p><em>Originally published at </em><a href="https://antonov.com.au/the-role-overlap-between-pm-and-pd"><em>https://antonov.com.au</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=099c11795487" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Managing My Week with a Notion Board]]></title>
            <link>https://mantonov.medium.com/managing-my-week-with-a-notion-board-33f550121f7b?source=rss-d151506cc83f------2</link>
            <guid isPermaLink="false">https://medium.com/p/33f550121f7b</guid>
            <category><![CDATA[notion-template]]></category>
            <category><![CDATA[time-management]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[weekly-planner]]></category>
            <dc:creator><![CDATA[Max Antonov]]></dc:creator>
            <pubDate>Fri, 05 Jul 2024 23:01:27 GMT</pubDate>
            <atom:updated>2024-07-05T23:01:27.177Z</atom:updated>
            <content:encoded><![CDATA[<p>I use Notion to plan and manage my week and I’ll take you through the process step-by-step. You can get the Notion Template <a href="https://productup.notion.site/07e03e2a2c314b009bbe2843f9364178">here</a>.</p><h3>Setting Up Your Week</h3><p>On Friday or Monday morning, I reflect on the priorities and goals that my team and I need to achieve. I then outline 1–3 of these goals and add them to my Notion Board. To ensure I have time and space to complete these goals, I often block out time in my calendar for them.</p><p>I add 🎯 to the goal cards so they are easily visible on the board.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/540/1*lMQKtFsLPTQuxyXKjgKU3w.png" /></figure><h3>Organising Tasks</h3><p><strong>This Week</strong> — This is what I want to or need to get done this week. If there are leftover tasks from last week, I reassess them and decide whether to keep them or move them to the “Later” pile.</p><p><strong>Later</strong> — This is for everything else. Sometimes this list gets a bit long, so I periodically purge tasks that have been sitting there and are clearly not that important or urgent, marking them as done.</p><p>Here’s how the board typically looks at the beginning of the week:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G9dbL-X1C-hK02g-jGZwBg.png" /></figure><h3>Reviewing Your Day</h3><p>I review how my Monday could look and how much I can get done based on the day’s events:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7HS48-nff9vKM1LT9C3haw.png" /></figure><p>At the end of Monday or Tuesday morning, the board might look like this: some tasks got done, some haven’t, and occasionally, an urgent task pops up that could affect productivity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OoLQYHPO_fvppyjhnqHh_Q.png" /></figure><h3>Focusing on Today</h3><p>The <strong>Today</strong> view helps to focus on today’s tasks:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fVOO-yKpj39DgXKV2Ryj5A.png" /></figure><h3>Reflecting and Planning Ahead</h3><p>On Friday, it’s time to reflect on the week and plan for the next week. Not everything gets done, of course. For tasks that haven’t been completed, I’ll reassess whether it still makes sense to complete them or move on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qxN7OsQp6iKUoQjRFf_e2Q.png" /></figure><h3>Archiving Completed Tasks</h3><p>Now let’s archive the completed tasks so they disappear from the board. I tag them with the year and month, but you can also go as granular as you like, e.g., weekly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/878/1*HBCvXb5TO1VL03Nhylt83w.png" /></figure><h3>Reviewing Achievements</h3><p>In the <strong>Done</strong> view, I can see what’s been accomplished in a particular month and what major goals have been achieved over the past year.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mt9JP1VHlJc2ZlPbY7D9lQ.png" /></figure><h3>Starting a New Week</h3><p>And then, the new week starts again:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KT8Kt5PX4DX-a98qin6vwQ.png" /></figure><p>Give it a go; duplicate the <a href="https://productup.notion.site/07e03e2a2c314b009bbe2843f9364178">Managing Your Week with a Notion Board Template</a></p><p><em>Originally published at </em><a href="https://antonov.com.au/managing-my-week-with-a-notion-board"><em>https://antonov.com.au</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=33f550121f7b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3 Quick Tips for Better Teamwork]]></title>
            <link>https://mantonov.medium.com/3-quick-tips-for-better-teamwork-2fa5617a7e29?source=rss-d151506cc83f------2</link>
            <guid isPermaLink="false">https://medium.com/p/2fa5617a7e29</guid>
            <category><![CDATA[team-collaboration]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[team-building]]></category>
            <category><![CDATA[leadership-skills]]></category>
            <category><![CDATA[teamwork]]></category>
            <dc:creator><![CDATA[Max Antonov]]></dc:creator>
            <pubDate>Sat, 29 Jun 2024 12:39:05 GMT</pubDate>
            <atom:updated>2024-06-29T12:39:05.562Z</atom:updated>
            <content:encoded><![CDATA[<p>Jun 28, 2024</p><p>So you want to build a stronger, faster team? Here are 3 quick tips for better teamwork that you can implement today:</p><h3>1. Transparency = Faster Improvements</h3><p>Show the team that it’s okay to make mistakes. A good place to start is with yourself.</p><p>Share your own mistakes with your team, especially when your boss is there too. When your boss suggests an idea in front of the team, share your perspective, even if it differs.</p><p>Soon you will start gaining insights from the team much faster about what processes or aspects of the product need fixing.</p><p><strong>Pro Tip:</strong> Share your mistakes, but don’t go crazy. While sharing mistakes is valuable, there should be a balance. Over-sharing or focusing too much on failures might undermine confidence in leadership. So, keep it balanced.</p><h3>2. Speed Up Decision Making Processes</h3><p>If you want to speed up your decision-making, one way is to hold a meeting. Meetings may not be great for context switching, scheduling, or avoiding interruptions, but if you are looking for speed, this is the way to go. You and the team need to be prepped for this.</p><p>Use tools like Notion or FigJam to outline the context, key points, and a suggested action plan before the meeting. This prep work shows your thinking process and helps everyone understand how you arrived at the conclusion and proposed decision. The team can spend the first 5–10 minutes reading it and then share their feedback: the good, the bad, and the ugly.</p><p>Process that feedback, adjust if needed, and make the call.</p><p><strong>Pro Tip:</strong> Disagreements are okay. As long as the team understands why and how a decision was made, it’s easier to move forward. At the end of the day, the decision-maker (you) needs to make the final call.</p><h3>3. Get to (really) know your team</h3><p>Make your Monday mornings special. Use Figma to share updates. The Figma template should have several sections, including what energised us over the weekend, upcoming events or celebrations, things we’ve learned or started doing, and our goals for the week. It’s a great format to set the tone for the week and lets you learn something new about your team.</p><p>For fun team activities, check out <a href="https://antonov.com.au/how-we-roll-team-activity">How We Roll: Team Activity</a>.</p><p><strong>Pro Tip:</strong> Ensure you have a couple of photos to share from the weekend and at least one thing you learned. These are great conversation starters!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/882/1*Tryom7lMKRJ6VgCtxAFvzg.png" /></figure><p><em>Originally published at </em><a href="https://antonov.com.au/3-tips-for-better-teamwork"><em>https://antonov.com.au</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2fa5617a7e29" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>