Leadership Without a Title: How to Get People On Board When You're Not 'The Boss'

Situation: Influence Without Formal Authority

In Agile teams, Product Owners, Scrum Masters, and other professionals often lack formal authority over colleagues. You're not the boss, but you need to convince people of a direction, priorities, or approach. How do you ensure they listen to you and follow your vision, without hierarchical tools?

‍

Influence Styles

‍

Relational

Good relationships and trust form the foundation. People are more likely to listen to you and support you if they respect you and if you take them seriously. So, take the time to truly get to know your colleagues and take their ideas seriously.

‍

Expertise

If you have strong subject matter knowledge or a thorough understanding of customer needs, people will see you as an authority in that area. This doesn't mean you have all the answers, but it does mean you understand the relevance and consequences of certain choices. For example:

• User Insights: “We spoke to 10 end-users, and 7 of them asked for X…”
• Domain Knowledge: “This feature is essential because…”

‍

Engaging Formal Sponsors

Sometimes there *is* a board or manager with formal power. Let them know your position and why a certain decision is important. If they endorse your vision, it provides support when there is resistance. Note: don't use this as a threat (“I'll tell your boss!”), but as additional justification.

‍

Cialdini's Techniques

• Reciprocity: If you help a colleague with their challenge, they are more likely to honor your request.
• Commitment: Get people to say yes to small requests step by step, so they gradually commit.
• Social Proof: Show that others (within or outside the organization) also follow this approach.
• Liking: People prefer to do something for someone they like.
• Authority: Refer to data, experts, or research. That is formal 'subject matter authority'.
• Scarcity: Emphasize time, opportunity, or competition—without exaggerating, of course.

‍

Facilitating instead of forcing

Ask questions so your conversation partner or team member gains insight into your argument themselves. Instead of saying, "Just do it this way," you can say: "What do you think will happen if we tackle feature X later?" This is Socratic: you let them think along and experience co-ownership.

‍

Assertiveness and boundaries

'Without authority' doesn't mean you have to accept everything. You can be friendly and firm:

• Explain why something doesn't fit within the scope, or not right now. And how it aligns with the product goals.
• Invite people to come up with alternatives, but be clear: this is the limit.
• Be empathetic in tone, but consistent in approach.

‍

Practical Example Scenario

Imagine the marketing department wants to launch a flashy feature for a trade show, but the dev team says it will jeopardize stability. As a PO, you don't have direct authority over marketing, but you can:

1. Relationship-based: Explain to marketing that you understand their needs, show that you grasp their KPIs.
2. Expertise: Show data or experiences demonstrating that stability is essential for customer retention.
3. Facilitation: Ask marketing what their real goal is (more leads?). Brainstorm an MVP version together.
4. Address Time and Risk: Indicate what will be lost if dev drops all stability work.
5. If Necessary: Go to the manager or executive who sets priorities for confirmation, if marketing truly won't budge.

‍

Conclusion

Without formal authority, you can still exert significant influence by leveraging engagement, respect, expertise, and subtle influencing techniques . In Agile teams, this is even the norm: you want teams with autonomy yet alignment. Through relational connection, clear arguments, and (if necessary) backing from formal sponsors, you achieve results without imposing everything top-down. This way, you build trust, buy-in, and better long-term collaboration.