r/Brighter

BI people often complain that business teams see them as “dashboard monkeys”. But if we’re completely honest, BI teams sometimes create this perception themselves.

Expample 1: Stakeholder: “Can you send me campaign performance data?” BI: sends CSV export.

WOW!

Now the stakeholder has: another spreadsheet, another version of the metric, another manually built report.

Two weeks later everybody asks why numbers don’t match across dashboards. Well, because nobody stopped to ask: “What are you actually trying to decide?”

Example 2: Business: “We need to understand why retention dropped.” BI: starts explaining joins, dbt models, refresh logic, attribution definitions, filter behavior.

But nobody answers the real business question.

A lot of BI communication is technically accurate - but its the accuracy that hides analyst from business problem.

Example 3: Stakeholder: “Can we visualize how revenue changed from last quarter?”

BI: “Technically Power BI/Tableau doesn’t support this natively…”

What could actually work:

Option 1: stacked bar with a running total column - builds in 20 minutes, works for most stakeholders, no custom visuals needed

Option 2: custom visual from AppSource - looks exactly like a waterfall, takes a couple of hours, harder to maintain when the data model changes

That's the answer. Two options, tradeoffs stated, stakeholder picks. The "not supported natively" part is irrelevant to them.

The 2026 Human Edge report is pretty direct about it: blind automation is the wrong path and will lead to business failures, and very quiclek.

Most AI failures aren't dramatic. The model doesn't go rogue. It just produces something slightly wrong, nobody catches it, and that error compounds through a pipeline until it's a real problem - a bad forecast, a flawed report, a decision built on garbage data. The failure is the missing human who would have noticed.

Which is why the role actually gaining value right now isn't "prompt engineer." It's the person with enough domain expertise to sense when an output doesn't smell right, even before they can explain why.

A few things that genuinely help here:

Knowing which errors to expect from which systems. LLMs hallucinate. Recommendation models amplify existing bias. Forecasting models quietly drift when the underlying data changes. These aren't random failures - they're predictable ones.

Domain depth over tool fluency. The people who catch AI mistakes aren't always the best at using AI. They're the ones who know the subject matter well enough to notice when something is off.

The companies that will struggle aren't the slow adopters. They're the ones moving fast while hollowing out the human expertise that made their outputs trustworthy. By the time they realize it, that institutional knowledge is already gone

A new global workforce report found that 39% of core job skills will change by 2030 - and the fastest-growing ones aren't technical. They're complex problem-solving, intuition, cognitive flexibility, and creativity. The things we used to dismiss as "soft skills" or "pre-industrial" are becoming the actual competitive edge in an AI-saturated market.

Think about what that means. The last two years were dominated by anxiety about Python, SQL, and whether your job title would survive the next model release. Meanwhile, the skills that are quietly becoming irreplaceable are the ones algorithms still can't fake: genuine curiosity, the ability to reframe a problem, knowing what question to ask before you run the analysis.

The report is pretty direct about why: true AI literacy won't mean less thinking. It will require more. Someone still has to decide what the output means, whether to trust it, and what to do when it's confidently wrong. That someone needs judgment - not just prompts.

The people who spent 2023 and 2024 optimizing for tool fluency may have been solving the wrong problem entirely.

New workforce research predicts that mandatory return-to-office policies will become "virtually unenforceable" by the early 2030s - because climate disruptions and geopolitical instability will make centralized offices logistically impossible. The distributed work era isn't ending. It's just on a very awkward pause.

Which means the people quietly building remote-ready skills and habits right now are positioning themselves better than they probably realize.

The logic in the report is straightforward: extreme heat events, flooding, and supply chain disruptions are already forcing ad hoc remote arrangements across industries. Geopolitical instability is making certain office locations genuinely risky. Companies that invested heavily in "return to office" infrastructure are going to find themselves holding a very expensive assumption. And knowledge workers - analysts, developers, strategists - are the most natural candidates for distributed work when that shift accelerates again.

A few things worth thinking about if you're in this space:

Your async communication skills matter more than your in-person presence. The people who thrive in distributed teams aren't just comfortable working alone - they write clearly, document decisions, and don't create bottlenecks that require a meeting to resolve.

Building a strong external reputation now is cheap insurance. When the office isn't the default, visibility inside your company becomes harder to maintain. People who have a presence outside it - a portfolio, a community, a track record that lives somewhere other than internal Slack - have more options.

Remote infrastructure is a skill. Knowing how to run a distributed project, across time zones, with clear ownership and minimal coordination overhead, is genuinely hard. The people who've figured it out will be in demand when the next wave of distributed work hits.

The companies currently fighting hardest for RTO aren't winning a culture war. They're burning goodwill on a policy that the next decade will quietly retire anyway