You have decided to adopt Power BI. Now the real work begins. How do you make sure the project succeeds? This guide gives you a proven 12-week project plan that actually works.

At Excel Department we have led 60+ Power BI implementations for Swedish companies. We have seen projects that take three months and deliver value from day one. We have also seen projects that drag on for two years and are never used. The difference is the methodology. This guide gives you the methodology that works.

Why most BI projects fail

Before we dive into the solution, let’s talk about the problems.

Gartner’s research shows: 70-80% of BI projects fail or do not deliver the expected value.

Common causes we have seen:

1. Big Bang approach “We’ll migrate all 50 reports in three months!” Result: chaos, missed deadlines, frustrated users.

2. IT-driven instead of business-driven IT builds what they think the business needs. The business doesn’t use it.

3. No training “Power BI is easy, people will figure it out.” Result: nobody uses the reports.

4. No data governance Different dashboards show different numbers. Nobody knows which one is right.

5. Perfectionism “We can’t launch until everything is perfect.” Result: the project drags on indefinitely.

Our methodology avoids all of these pitfalls. Iterative delivery, business focus, training from day one, data governance from the start.

Project plan: 12 weeks from decision to value

We divide the implementation into six phases. Each phase has clear deliverables and decision points.

Phase 1: Discovery and strategy (Weeks 1-2)

Purpose: Understand the current situation, define goals, create a roadmap.

Week 1: Current-state analysis

Activities:

Workshop with key people (4 hours): – Which reports do you use today? (Excel, other systems) – Which decisions are based on the reports? – What works well? What is painful? – What are your most important KPIs?

Data source inventory: – List all systems with data (accounting system, CRM, Excel files, databases) – Identify data owners – Document how data is updated today – Assess data quality

User interviews (5-10 people): – CFO, controllers, sales manager, operations manager – Which reports do they need? – How do they make decisions today? – What are they missing?

Output: – Documented list of existing reports – Data source map – User needs and pain points

Week 2: Strategy and prioritisation

Activities:

Define success measures: What does “successful implementation” mean? – Time savings? (X hours/month) – Faster decisions? (From weeks to days) – Better insights? (Find X unprofitable customers) – User adoption? (X% use it regularly)

Prioritise reports: Use a simple matrix:

Report Business value (1-5) Complexity (1-5) Priority
Sales dashboard 5 2 High
Cash flow forecast 5 4 Medium
HR statistics 2 2 Low

Choose 1-2 with high value and low complexity as a pilot.

Define roles: – Sponsor: CEO or CFO (decision authority, budget) – Project manager: Drives the project day to day – Data champions: 2-3 people who learn Power BI – IT contact: Gateway, security, infrastructure – Super users: 5-10 people from different departments

Create a roadmap:

Månad 1-3: Pilot (1-2 rapporter)
Månad 4-6: Skalning (5-10 rapporter)
Månad 7-12: Vidareutveckling och optimering

Output: – Defined success measures – Prioritised report list – Role matrix with names – 12-month roadmap – Budget and resource plan

Decision point: Go/No-go for the pilot phase.

Phase 2: Pilot implementation (Weeks 3-6)

Purpose: Build 1-2 reports, learn the tool, prove the value.

Week 3: Data source integration

Activities:

Connect the pilot report’s data sources: – Install Power BI Gateway if necessary – Configure database connections – Set up authentication and security – Test the connection

Power Query transformation: – Clean and structure data – Create staging tables if necessary – Document transformations – Validate data quality

Time: 2-3 days for a report with 2-3 data sources.

Output: Working data flow from source to Power BI.

Week 4: Data modelling and development

Activities:

Create the data model: – Define fact and dimension tables – Establish relationships – Create a date table (critical for time analysis) – Optimise for performance

Develop measures (DAX): – Define all KPIs – Create time-based comparisons (YTD, previous year, etc.) – Document calculation logic

Build visualisations: – Design with user feedback – Max 6-8 visuals per page – Add filters and slicers – Format according to the company’s visual identity

Time: 3-5 days depending on complexity.

Output: Finished report in Power BI Desktop.

Week 5: Testing and validation

Critical step: The report must show the right numbers.

Activities:

Data validation: – Compare Power BI with the existing Excel/system row by row – Document discrepancies – Adjust calculations until all numbers match – Get approval from the data owner

User testing: – 3-5 end users test the report – Observe how they interact (don’t just ask) – Collect feedback on layout, functionality, performance – Adjust based on feedback

Performance testing: – Measure load time (should be <5 seconds) – Optimise slow visuals – Test on different devices (desktop, tablet, mobile)

Time: 3-5 days.

Output: Validated report ready for publishing.

Week 6: Publishing and pilot launch

Activities:

Publish to Power BI Service: – Create a dedicated workspace – Publish the report – Configure scheduled refresh – Set up security and permissions

Training for pilot users: – 1-hour workshop per user group – Show how to open the report – Demonstrate interactivity – Share documentation

Monitor usage: – Power BI Usage Metrics – Collect feedback from users – Note questions and problems – Respond quickly to issues (same day)

Time: 2-3 days.

Output: – Published and working report – Trained users – Documentation (user guide, technical documentation)

Decision point: Pilot successful? Continue to scaling. Problems? Adjust the approach.

Phase 3: Training and skills development (Weeks 7-8)

Purpose: Build internal capacity to scale.

Week 7: Data champion training

For the 2-3 people who will build reports:

Day 1: Power BI Desktop basic course – Connecting data sources – Power Query transformations – Creating visualisations – Basic DAX

Day 2: Data modelling – Facts vs dimensions – Relationships and cardinality – Star schema best practices – Performance optimisation

Day 3: Advanced DAX – Time intelligence (YTD, previous period, etc.) – Context handling (CALCULATE, FILTER) – Common calculation patterns – Troubleshooting

Day 4: Publishing and administration – Power BI Service overview – Scheduled refresh – Security and RLS – Gateway configuration

Day 5: Practical exercise – Build a report from scratch – From data source to published report – With feedback and coaching

Time: 5 days of intensive training.

Output: 2-3 people can build their own reports.

Week 8: Organisation and governance

Activities:

Establish data governance: – Define a “single source of truth” for KPIs – Create a glossary for measures (what does “Total sales” mean?) – Document calculation logic – Establish an approval process for new reports

Create templates and best practices: – Report templates with the company’s visual identity – Naming conventions for measures and columns – Documentation templates – Power Query templates for common data sources

Security strategy: – Define which workspaces are needed – Role-based permissions – Row-level security strategy – Data classification (public/internal/confidential)

Output: – Governance document – Templates – Security framework

Phase 4: Scaling (Weeks 9-10)

Purpose: Build 5-10 prioritised reports.

Weeks 9-10: Parallel report development

Strategy: Different people build different reports at the same time.

Example allocation: – Data champion 1: Finance dashboards (3 reports) – Data champion 2: Sales dashboards (2 reports) – Consultant (if engaged): Complex integrations (2 reports)

Daily standup (15 min): – What did I do yesterday? – What am I doing today? – Blockers?

Weekly review: – Show progress to the sponsor and stakeholders – Get feedback early – Adjust priorities as needed

Output: 5-10 production-ready reports.

Phase 5: Organisation-wide launch (Week 11)

Purpose: Roll out to the whole organisation.

Week 11: Launch and training

Activities:

Communication plan: – Email to all users 1 week before launch – What is Power BI? Why are we switching? – Links to reports – Book training sessions

End-user training: – 30-minute sessions per department – Show the reports relevant to them – Hands-on exercise – Questions and answers

Support setup: – Dedicated Teams channel for questions – FAQ document – Quick response from data champions (same day)

Go-live: – Activate all reports at the same time – Monitor usage during the first week – Proactive follow-up with departments

Output: All users have access and basic knowledge.

Phase 6: Optimisation and further development (Week 12+)

Purpose: Continuous improvement.

Week 12: Evaluation

Measure success against defined goals: – Time savings: How much time is saved on manual reporting? – User adoption: How many open reports regularly? – Decision pace: Have decisions become faster? – ROI: Costs vs benefits

Collect feedback: – Survey to all users – In-depth interviews with key people – What works well? – What can be improved?

Identify the next wave: – Which reports should be built next? – New data sources to integrate? – Advanced features to introduce?

Output: Evaluation report and plan for the next 6 months.

Roles and responsibilities

Clear roles are critical for success.

Role Responsibility Time commitment
Sponsor (CFO/CEO) Decisions, budget, communicating the importance 2-3 hrs/month
Project manager Drives the project day to day, coordination 50% of a full-time role
Data champions (2-3) Build reports, support users 50% in phases 2-4, then 20%
IT contact Gateway, security, infrastructure 10-20 hrs in total
Super users (5-10) Help colleagues, collect feedback 5% ongoing

Budget: What does it cost?

Internal cost (staff): – Project manager: 0.5 FTE × 3 months × SEK 500/hr × 176 hrs/month = ~SEK 130,000 – Data champions: 3 × 0.5 FTE × 2 months × SEK 500/hr × 176 hrs/month = ~SEK 265,000 – Other (meetings, testing, etc.): ~SEK 50,000 – Total internal cost: ~SEK 445,000

External cost (if a consultant is engaged): – Discovery and strategy: SEK 40,000 – Training (5 days): SEK 50,000 – Pilot development: SEK 60,000 – Coaching during scaling: SEK 80,000 – Total external cost: ~SEK 230,000

Licence costs (year 1): – Power BI Pro: 50 users × SEK 70/month × 12 = SEK 42,000 – Gateway (runs on an existing server): SEK 0 – Total licence cost: ~SEK 42,000

Total project cost: 445,000 + 230,000 + 42,000 = ~SEK 717,000

ROI example: If the project saves 40 hours/month in manual reporting work: – Savings: 40 hrs × SEK 500 × 12 months = SEK 240,000/year – Payback: 717,000 / 240,000 = 3 years

But the savings are often larger, and hard-to-value benefits (faster decisions, better insights) add value.

Critical success factors

After 60+ implementations we know what determines success:

1. Management commitment

If the CEO or CFO doesn’t care, nobody else will. The sponsor must: – Communicate the importance regularly – Use the reports personally – Prioritise the project when resource conflicts arise

2. The right pilot report

The first report sets the tone. Choose one that: – Is important enough that people care – Is not so critical that mistakes have catastrophic consequences – Has clear data sources – Can be built in 3-4 weeks

3. Training from day one

Don’t wait until the end for training. Data champions start learning in week 1. End users get an introduction when the pilot launches.

4. Iterative delivery

Launch pilot → learn → adjust → scale. Not big bang.

5. Data governance from the start

If different reports show different numbers, trust collapses. Establish a “single source of truth” from day one.

When you should hire a consultant

You can run the project yourselves, but consultant help speeds things up and reduces risk.

Hire a consultant if: – You lack Power BI expertise internally (nobody has used it before) – Tight deadline (must be done in 3 months) – Complex data source integration (many systems, APIs, legacy) – You want to avoid common mistakes – You need to train an internal team

Excel Department can help with: – Leading the whole project (from discovery to launch) – Building the pilot report together with your team – Intensive training for data champions (5 days) – Coaching during scaling (weekly check-ins) – Review and quality assurance

Contact us for a free consultation (30 min) and a tailored quote.

Checklist: Are you ready to start?

If all are ticked: get going. If several are missing: start there.

Next steps:

  1. Book a kickoff meeting with the sponsor, project manager and IT
  2. Carry out weeks 1-2 (discovery and strategy)
  3. Decide on internal vs external delivery
  4. Start the pilot phase

Related guides: – Power BI for business: Complete guide – Migrating from Excel to Power BI – 5 Power BI dashboards every CFO needs


Contact Excel Department: – Phone: 010-264 20 20 – Email: info@exceldepartment.se – Address: Slottsbacken 8, 111 30 Stockholm

Need help with this? Our Power BI consultants can help you – the first consultation is free of charge.

Book a free call or phone 010-264 20 20.