Gareth Stretch

1. Introduction
2. What is Listen First, Advise Second?
   1. Active Listening in Action (Fabric Example)
   2. Why Listening Matters in the Microsoft Fabric Context
3. Lets Make This Practical.
   1. 1. Realizing Client Goals Through Active Listening
      1. Key Example: Uncovering Business Drivers Beneath Technical Requests
      2. Why This Matters in Fabric:
   2. 2. Adapting Recommendations to Client Expertise and Maturity
      1. Key Examples: Educating Less-Experienced Clients:
      2. Key Examples: Optimising for Seasoned Clients:
      3. Why This Matters in Fabric:
   3. 3. Avoiding Prescription Before Diagnosis
      1. Key Example: Avoiding Overengineering with a Careful Approach
      2. Why This Matters in Fabric:
   4. 4. Building Trust and Credibility
      1. Key Example: Empowering Client Teams by Addressing Concerns
      2. Why This Matters in Microsoft Fabric Solution Design:
4. Why Listening Matters Uniquely in the Microsoft Fabric Ecosystem
   1. Complexity Across Silos:
   2. Configurable but Overlapping Tools:
   3. Balancing Technical Depth with Business Context:
5. Techniques for Practicing “Listen First, Advise Second”
6. Core Challenges: The Pitfalls of Not Listening First
7. Conclusion : The True Power of Listening
8. A Challenge for you, the reader
   1. You might also like
   2. Related posts

In my previous article, I introduced the concept of The 7 Consulting Principles Every Microsoft Fabric Consultant Should Live By. I covered each topic lightly. This page is dedicated to Principle 1: Listen first, advise second.

Introduction

Early in my consulting career, I was in a high-pressure kick-off meeting with a fast growing start-up digital bank. They were struggling with their analytics architecture. They laid out a flood of frustrations: sluggish Power BI dashboards, sprawling data pipelines, and escalating cloud costs. Eager to demonstrate technical expertise and provide value, I rushed to suggest solutions: optimising SQL Warehouse performance, migrating workloads to Microsoft Fabric, and fine-tuning Power BI datasets. Everyone seemed impressed and we left the meeting with a clear plan of action.

Weeks later, the metrics looked marginally better, but the real problem persisted. Performance wasn’ the root cause. The issue was operating-model shaped: no accountability for self-service analytics, mistrust in data governance, and fragmented workflows. I had addressed the symptoms while completely overlooking the root causes. Had I listened more intently, asked broader open-ended questions about organisational dynamics and technology, I could have uncovered these issues from day one and implemented the right solution accordingly.

This misstep was humbling, but it taught me a crucial lesson that applies to every analytics consultant: technical expertise isn’t enough. With a platform as versatile as Microsoft Fabric, success starts with mastering discovery. Listen deeply, then advise.

Listen First, Advise Second, is especially relevant for Microsoft Fabric implementations, where aligning modular capabilities like Data Factory, Lakehouses, Warehouses, and Power BI with client priorities can make or break project success. Whether you’re a rookie or seasoned expert, taking time to listen deeply fosters better collaboration which results in the implementation of tailored solutions that resonate with both the business vision and technical landscape.

What is Listen First, Advise Second?

By actively listening you’re able to fully grasp the client’s business context, technical environment, and goals ensuring any recommendations are not only technically sound but also genuinely aligned with the client’s specific needs.

Practical listening goes beyond simply hearing words:

• Ask thoughtful, open-ended questions.
• Confirm your understanding to eliminate assumptions.
• Read between the lines to uncover unspoken priorities, challenges, or risks influencing the client’s decisions.

Do this well and your advice becomes purposeful, strategic, and actionable addressing both immediate concerns and long-term objectives in a way that resonates with your client.

Active Listening in Action (Fabric Example)

A retail client once asked me for a real-time analytics solution. They were eager to use Microsoft Fabric’s Lakehouse and insisted on achieving ‘real-time’ insights. The initial instinct was Microsoft Fabric Data Pipelines or Synapse Real-Time Analytics, to continuously load data into the Lakehouse, which would then feed into Power BI for near real-time visualisation.

However, before jumping into execution, I knew it was crucial to fully understand what “real-time” meant to the client, so I took a step back to clarify:

• “Which decisions truly need real-time?”
• “How often does the source date update?”
• “What challenges are you facing with today’s reporting system?”

Through these discussions, I started uncovering details that fundamentally shifted my understanding of their needs:

1. Misaligned Terminology:
   When the client said “real-time,” they weren’t referring to continuously streaming data. Instead, they simply needed their reports to refresh daily so they could use them in their morning operational meetings. This insight clarified that achieving true real-time analytics was unnecessary for their requirements.
2. Unnecessary Complexity:
   Their existing data pipelines already operated in batch mode, and the architecture wasn’t designed to support real-time streaming ingestion. Switching to real-time capabilities would have introduced avoidable technical complexity, effort, and cost.
3. The Real Pain Point:
   The crux of their problem wasn’t the lack of real-time data, it was the difficulty in consolidating data from multiple disparate systems into meaningful reports. They wanted seamless, overnight updates that would break down silos and provide aggregated insights for decision-making.

Armed with this deeper understanding, I realised the best approach wasn’t to immediately implement the solution they had initially asked for. Instead, I proposed a different solution tailored to their actual needs. I recommended:

• Using Microsoft Fabric’s Data Pipelines (formerly Data Factory in the Fabric context) to ingest and stage their data in a Fabric Lakehouse.
• Building a Fabric Warehouse on top of the Lakehouse to enable efficient SQL-based reporting.
• Configuring Power BI to connect to the Warehouse or Lakehouse for visualisation, with scheduled refreshes aligned to their daily reporting requirements.

The Results:

The result was clear, consolidated morning resports and no over-engineering with unnecessary streaming technologies. By aligning the technical implementation with their business requirements and maturity, the client was able to achieve the insights they needed efficiently and cost-effectively.

This experience became a foundational reminder of the power of active listening and why Listen First, Advise Second is such an essential principle especially in the context of Microsoft Fabric’s versatile ecosystem.

Why Listening Matters in the Microsoft Fabric Context

Microsoft Fabric is a versatile and complex platform, offering overlapping and complementary tools. While powerful, its flexibility can lead to misaligned implementations if a consultant doesn’t first put the effort in to deeply understand the nuances of the client’s needs.

1. Capability Overlap and Nuance:
   • Microsoft Fabric offers multiple ways to solve a problem e.g., choosing between a Lakehouse for unstructured data modernisation versus a Warehouse for structured, SQL-based analytics. Without understanding the client’s data culture, maturity, and goals, a consultant might recommend a clever solution, but one that doesn’t fully address the client’s need.
   • Similarly, Dataflows and Pipelines have overlapping ingestion capabilities, but their use depends on the complexity, frequency, and transformations required.
2. Varying Client Maturity Levels:
   • Technically Seasoned Clients:
     These clients may already have workflows in place and are looking to optimise processes or adopt advanced features, like real-time analytics or machine learning models. Covering data foundations and governance can be a waste of resources.
   • New or Less Mature Clients:
     These clients may not yet understand the difference between a Lakehouse and a Warehouse or appreciate the importance of steps like data governance or intermediate staging layers. Simplifying concepts and carefully explaining capabilities ensures meaningful progress without overwhelming them.
3. Complexity of Cross-Functional Collaboration:
   Fabric projects often affect multiple business units from IT to Operations to Finance. Meaningful listening aligns incentives and prevents new silos.

Lets Make This Practical.

In the realm of Microsoft Fabric, where technical complexity often takes center stage, meaningful listening can be the most crucial consulting skill. Microsoft Fabric’s ability to unify disparate systems, support diverse data formats, and offer overlapping configurable components requires a deep understanding of the bigger picture. Here are four patterns where listening shifts the solution:

1. Realizing Client Goals Through Active Listening

Translate what they ask into what they need

Key Example: Uncovering Business Drivers Beneath Technical Requests

• Scenario: A client requests a financial reporting solution using Microsoft Fabric’s Warehouse capabilities.
• Initial Technical Focus: Build SQL-based reporting models.
• Reality Uncovered Through Listening: The client’s real pain point is integrating SAP Finance and CRM systems into self-service reporting.
• Advice: Instead of rushing into Warehouse implementation, recommend designing a data ingestion pipeline to harmonize SAP and CRM data into a Fabric Lakehouse, enabling meaningful Power BI dashboards.

Why This Matters in Fabric:

Fabric’s ability to harmonise siloed data across systems means consultants must understand the underlying business drivers to design holistic solutions. Failing to listen risks delivering narrowly-focused implementations that neglect long-term scalability or flexibility.

2. Adapting Recommendations to Client Expertise and Maturity

Tailoring advice to a client’s expertise and readiness fosters collaboration and ensures solutions are both digestible and actionable. For less mature clients, this may mean simplifying concepts, focusing on foundational capabilities, and introducing complexity gradually. For seasoned clients, the emphasis shifts to performance optimisation, advanced use cases like real-time analytics, or leveraging AI.

By meeting clients where they are, consultants can demystify the platform, build confidence, and guide realistic adoption paths. This approach empowers rather than overwhelms, improving both adoption rates and the long-term success of Fabric implementations.

Key Examples: Educating Less-Experienced Clients:

• Scenario: A client insists on direct data ingestion from SAP into Power BI for real-time insights, bypassing Fabric’s Lakehouse.
• Listening Insight: The client is unaware of intermediate staging benefits, such as transformation, security, and schema validation.
• Advice: Educate the client on the strategic value of Lakehouses, suggesting foundational steps like building scalable ingestion pipelines.

Key Examples: Optimising for Seasoned Clients:

• Scenario: A technically mature client with existing workflows seeks to reduce pipeline latency for real-time analytics.
• Listening Insight: The client prioritises speed and already has basic governance in place.
• Advice: Recommend leveraging advanced features, such as Synapse GPU-driven Real-Time Analytics, focusing on pipeline performance optimisation.

Why This Matters in Fabric:

Fabric’s tools are highly configurable yet overlapping, creating multiple paths to achieve similar outcomes. Without listening, consultants risk mismatched recommendations either overly simplistic or needlessly complex solutions.

3. Avoiding Prescription Before Diagnosis

Fabric implementations must align with the client’s infrastructure, strategic roadmap, and organisational culture. Rushing to apply a “one-size-fits-all” solution or favoring the consultant’s preferred technical features can lead to project misalignment.

Key Example: Avoiding Overengineering with a Careful Approach

• Scenario: A consultant wants to recommend Fabric’s advanced Synapse GPU-driven AI capabilities.
• Listening Insight: The client lacks a usable data foundation and governance model to support advanced functionality.
• Advice: Recommend foundational steps, such as developing modular pipelines and scalable Lakehouses, before introducing advanced analytics.

Why This Matters in Fabric:

The flexibility of Microsoft Fabric is both its strength and its challenge. Without a thoughtful diagnosis, there’s a risk of proposing overengineered solutions that increase costs or exceed the client’s readiness.

4. Building Trust and Credibility

In a technical environment like Fabric, trust complements technical excellence. Clients prioritise relationships and collaboration as much as the technical solution itself. Listening deeply demonstrates empathy and ensures that technical advice aligns with the client’s unique concerns.

Key Example: Empowering Client Teams by Addressing Concerns

• Scenario: A client CEO mentions their IT department feels overwhelmed by the complexity of integrating systems into Fabric.
• Listening Insight: The technical team lacks sufficient onboarding and support, which hinders their ability to adopt Fabric effectively.
• Advice: Offer lightweight solutions like proof-of-concept pipelines, onboarding workshops, and transparent documentation templates to empower their team, gradually building confidence in Fabric’s capabilities.

Why This Matters in Microsoft Fabric Solution Design:

Fabric projects often involve cross-functional teams and business silos. Listening builds trust and ensures that recommendations resonate across stakeholders, fostering a partnership rather than a transactional relationship.

Why Listening Matters Uniquely in the Microsoft Fabric Ecosystem

Complexity Across Silos:

Fabric unifies disparate systems and data formats, so the “bigger picture” must be understood across domains such as IT, Finance, and Operations. Active listening is vital to uncover interdependencies and hidden silos.

Configurable but Overlapping Tools:

Fabric’s components (Lakehouse, Warehouse, Dataflows) are powerful but overlapping. Choosing the right path depends on technical maturity and business priorities, a judgement that only comes through meaningful dialogue.

Balancing Technical Depth with Business Context:

Fabric sits at the crossroads of business and technical innovation. Listening enables consultants to align cutting-edge technical capabilities with practical business applications.

Techniques for Practicing “Listen First, Advise Second”

1. Ask the Right Questions: Open with prompts that surface priorities, constraints and context:
   • What are the key business outcomes you’re hoping to achieve with Fabric in the next 3-6 months?
   • What are the constraints, risks, or dependencies you’re facing today?
   • How do your teams work with data today and what does your ideal look like?
   • How does this initiative fit your wider strategy and digital transformation goals?
   • What tools and platforms are in play and how well do they interoperate
   • What does success look like and how will we measure it?
2. Validate Your Understanding: Paraphrase or summarise their responses to confirm alignment:
   • “So if I understand correctly, your main concern is… and what you’re looking to solve for is…”
   • “It sounds like the goal is to streamline reporting for your sales team; is that accurate?”
3. Hold Back the Urge to Jump to Solutions: Fight the urge to immediately respond with technical advice. Take the time to process what’s been shared before crafting a recommendation:
   • “That’s a great point. Let me take a closer look at how we can address that in the context of your other priorities.”
   • “Let me review governance, cost and latency implications, then propose the best path.”

Core Challenges: The Pitfalls of Not Listening First

Pitfall 1 : Jumping to Solutions too quickly

• Misaligned advice: recommending real-time streaming when the real issue is data quality or governance.
• Wasted effort: building complex workflows that fail to address core business outcomes.

Pitfall 2 : One-Size-Fits-All Approach

• Assuming every client benefits from advanced Fabric features, regardless of maturity.
• Overlooking basics such as legacy dependencies or poor data hygiene.

Pitfall 3 : Ignoring Organisational Change Resistance

• Poor adoption due to lack of user training or support.
• Misalignment between IT, operations, and business stakeholders.

Pitfall 4 : Focusing on Symptoms, Not Root Causes

• Superficial fixes (e.g., faster dashboards) that ignore fragmented ingestion or governance issues.

Pitfall 5 : Losing Non-Technical Stakeholder Engagement

• Overemphasising Fabric’s technical capabilities rather than business outcomes such as ROI or speed-to-insight.

By avoiding these pitfalls, consultants can deliver aligned, sustainable, and relevant solutions that ensure the successful adoption of Microsoft Fabric.

Conclusion : The True Power of Listening

“Listen First, Advise Second” is more than a consulting principle — it is the foundation for delivering solutions that genuinely matter. In the world of Microsoft Fabric, where technical versatility meets business complexity, deep listening allows consultants to bridge gaps, align priorities, and unlock transformative value. As we’ve seen, active listening helps address not only technical challenges but also organisational dynamics, ensuring recommendations resonate at both strategic and tactical levels.

The lesson is clear: every client conversation is an opportunity to uncover hidden needs, challenge assumptions, and build trust. Technical expertise may establish credibility, but meaningful listening cements your reputation as a trusted advisor. Mastering this approach is what turns Fabric projects into lasting success — not just faster dashboards or leaner pipelines, but solutions that empower organisations to thrive.

A Challenge for you, the reader

In your next project, or even your next client conversation, make “Listen First” your guiding principle. Before mentioning a technical solution, commit to asking three thoughtful, open-ended questions that uncover deeper priorities and pain points. Validate what you’ve heard, resist the urge to leap straight into action, and align your approach with the client’s broader goals.

Can you shift from solving problems in isolation to solving them holistically? From being a technical expert to becoming a trusted partner who delivers real business outcomes? Challenge yourself to listen deeply, lead with empathy, and trust that impactful solutions begin with understanding. The results may surprise you and they will undoubtedly elevate your consulting game.

You might also like

If you liked this article, follow me on LinkedIn to stay up-to-date with my latest posts. You might also like the following posts about related topics: