[Nayara Hellen] - The colors have diminished. But the possibilities have grown.
The Brick Chronicle reimagines the story of LEGO as a vintage newspaper, turning the entire Rebrickable database into an editorial data story. Across 4.6 million catalogued pieces, 27,069 sets, 26,971 minifigures, 61,674 distinct parts, 494 themes and 273 colors, it investigates a single, surprising paradox at the heart of the brick: as LEGO's active color palette contracted, its complexity, specialization and creative potential exploded. The report follows that thread page by page. Neutral tones (black, light gray and white) alone account for roughly 48% of every brick ever produced, and the once-expanding rainbow eventually thinned out. Yet in the same era, the average set grew about 3.9 times larger in piece count (2000 to 2025), and the variety of distinct parts released each year climbed about 2.6 times (1997 to 2025). Fewer colors, but far more ways to build. LEGO did not shrink. It evolved. Every visual is hand-built as a custom HTML and SVG measure in DAX, over an aged-paper newspaper layout with serif typography and a restrained ink-and-red palette, so the analysis reads like a broadsheet rather than a dashboard. The edition closes with an interactive finale: a fully in-report "Build Your Minifig" studio where the reader assembles their own minifigure, head to legs, entirely with CSS, the perfect closing note for a story about endless combinations. eyJrIjoiNWY4NzU0N2ItZWY2OS00ODlkLThjZjQtNGUwYWQ5MTUxMDJkIiwidCI6Ijc2OGM1NWMwLWViNjktNDhiZC04ODYyLWQ2ODYwZjU4NWVkNiJ9World Champ BCN 2026 Round 3: What Truly Makes a Movie Successful?
Movies have always been an interesting topic! The raw TMDB dataset was initially very messy, resulting in many‑to‑many relationships that made analysis difficult. After cleansing, the data became one‑to‑many, which made it more approachable and reliable for analysis. I applied several filters to ensure validity: 1. Only films with status Released 2. Minimum vote count ≥1,000 to capture a wider and more realistic range 3. Budget ≥$1,000 for realistic production values 4. Revenue >0 5. Release date ≥1900, since earlier data was too sparse to analyze 6. Non‑duplicate values Columns were renamed for clarity, poster/backdrop paths standardized with TMDB links, and outliers were kept visible to allow responsible interpretation. Dashboard highlights: Page 1 features a radial chart inspired by web patterns (I'm a peter parker!), summarizing movie releases against budget, revenue, and vote average, built by calculating angle and radius. Pages 2–4 allow toggling between Exclude Outlier, Include Outlier, and Outlier Only, so users can evaluate insights with or without extreme cases. All charts include alt text and structured tab order to comply with accessibility standards. Hope i'm not over-engineered this report haha. Thanks! - Ahmad Ulfi Jihad DzulqornainWorld Champs BCN 26 - Finale - SQL Radar · Find the signal before the alarm
Hello the Community, Here is my Barcelona Finale report. Nothing's broken. Officially. That was my starting point: no SQL system had crossed a critical threshold, yet several were clearly drifting. So I built this report around three simple questions, one page each: 1. Signal: where are the problems? A pill table shows, for every system, its threshold, headroom and drift status. Three charts and a map show what is moving, and where. 2. Diagnosis: why is it moving? For the selected system, a timeline shows when each metric left its August normal, and a table checks every metric against the last assessment: is it new, is it explained, is it shared with another system? 3. Action: what do we do first? A criticality-versus-signal matrix and a runway timeline rank the systems, and the plan gives each one an action and a deadline. One click sends the brief by email. On the design side, I deliberately split the work in two. Native visuals carry the data and the interactions (the table that filters the page, the charts, the matrix and their report-page tooltips). HTML carries the experience: the map that zooms on the selected site, the animated timelines, the identity cards and the intro. And there is a little assistant on every page. In light mode, Mercury, a drop of liquid metal, sums up the page in one sentence and answers a few questions. Switch the light off, and Glitch, a pixel bug who lives in your SQL logs, takes over with the same insights and a lot more attitude. Find the signal, understand it, act on it. Hope you enjoy the ride! You liked my report ? You can find me here on linkedin for more content : Aanor Le Gouic | LinkedInWorld Champs BCN 26 - Finale - AstraVale - Operational Health
This report was built from the perspective of an AstraVale employee responsible for keeping the company’s systems running reliably. It is designed to answer three questions: Which systems need attention? What happened? And are there other related systems that could also be affected? Operational Overview - Which systems need attention? This page gives an overall picture of system health and helps the user decide where to start. You can get an immediate picture of system health from the KPI cards at the top. They show how many systems need investigation, how many need review or watching, and how many are within limits. You can click each card to focus on that group of systems. The "Where to focus" table shows which systems need investigation, which need review, and which should be watched. The trend beside each system shows the pattern of recent breaches, while the signal squares explain which rules have been met and contributed to its priority. Users can hover over the information icon to learn what those rules mean. The interactive globe adds a view of the facilities and lets the user narrow the page to one location. The assessment summary shows where checks have failed and how serious those findings are. System Investigation - What happened? After identifying a system that needs attention, the user can explore it in more detail on this page. The system information "i" icon provides context about its purpose and importance, while the monitoring visuals help explain its behaviour. The heatmap makes it easier to spot unusual days and see which metrics were involved. The "Top priority" mark highlights the metric to look at first, giving you a clear starting point for your investigation. You can then select a metric and use the hourly chart to see when it changed, how long the issue lasted, and whether it returned to its expected range. This helps distinguish a short spike from a more sustained issue. The assessment history provides another part of the picture. It shows how check results have changed between assessments, helping the user see whether findings are new, recurring, or have been resolved. Connected Operations - Could related systems also be affected? This page helps the user look beyond a single system. Systems can be grouped by a shared dependency, physical facility, hosting region, or another connection. These relationships show where it may be useful to investigate next. The percentages beside each system show how its average changed between the selected baseline and comparison periods. This gives a quick way to see which systems changed the most. The line chart shows how that change developed day by day. In the relative view, every point compares that day’s average with its baseline. This makes it easier to see whether related systems changed at a similar time or followed different patterns. ---------------- The finals were an incredible experience, and I'm so grateful for everything I learned, the people I met, and the chance to be part of it all!😄 If you’re thinking about participating, go for it – I promise it’s an experience you won’t forget!😀World Champs BCN 26 - Finale - The Weight of Waiting by Jerome Ian Arbonida
THE WEIGHT OF WAITING Landing What if I told you that the most technical dataset I have ever received… could teach us something very human? This is The Weight of Waiting. Someone is waiting while systems are working. We can measure the delay. But what does that delay take away? Welcome to Astravale. Page 1 This is the world of Astravale. Equal — but not in weight. Each site carries a different weight, represented through four signals: Workload, Pressure, Room, and Waiting. And when we sliced the data to the latest date, something stood out. Only one site remained in red. And since waiting has weight… we should meet the Weightbearer. Page 2 This is the Atacama Deep Space Station, carrying the weight of Astravale through its Mission Critical Helios Telemetry system. The data starts to tell us a story. As activity rises, pressure rises with it. Memory and storage remain relatively stable, following their own trends. But one signal caught my attention. Waiting. As activity increases, blocked sessions and deadlocks increase too. So the question becomes: Is the system failing? Let’s go deeper. Page 3 Still in Atacama, we can again see activity rising significantly. But technical findings? They stay flat. And that tells us something important. The system isn’t failing. It’s working. It’s just… overworked. And who carries the consequence of that? Us. The humans behind the systems. Page 4 And now… I want to reveal the true weight of waiting. Because in this world of data, technology, and AI… let this dashboard remind us: our currency isn’t tokens. It’s time. [25-second interaction / show what happened to Astro that day] Maybe you can relate to Astro. As a parent. A brother. A sister. Or maybe… some of us were once the Astro who waited. So my hope is simple: Let’s unload the weights. I hope we don’t miss a home-cooked meal while we make our systems more efficient. I hope we don’t miss a bedtime story while we turn pressure into performance. I hope we always get to say goodnight. And when home finally gets quiet… I hope we still have a little energy left to give. Because behind every workload, every alert, every data point… there is a human being waiting for someone. And as we leave this conference and go home to the people we love… I hope we remember to thank them. The ones who patiently, quietly, and lovingly… carried the weight of waiting with us. Gracias, Barcelona. Maraming salamat, at mabuhay tayong lahat. Thank you.World Champion Winner - Live Finale Build - AstraVale SQL health report by Marius Helle
🏆 2026 Power BI Dataviz World Championship Fabcon Barcelona finale winner. AstraVale SQL health report The report takes the reader from a broad overview to a clear plan. It starts with all systems, then narrows down to what has changed, why it happens, how the problems are connected, and what to do first. Each page builds on the one before. Overview: shows all systems on a map and in a table, coloured by status, with equipment value and alarms. The buttons filter the view to all systems, those getting worse, or those that are steady. Problems: compares each system with its own August level to separate new problems from old ones. The buttons switch between where to start (equipment value against rising metrics), recent changes (a heatmap of every metric), and where the alarms come from (alarm hours per metric). Causes: looks at why the problems happen. The buttons switch between memory use over an average day, comparing servers the company runs itself with Azure SQL, and a chain that follows how strain builds up from CPU to blocked sessions and deadlocks. Connections: follows disk load day by day for the systems that are getting worse, compared with their own August level. The buttons test two possible links between them: systems at the same site, and systems that read from the same data feed. Action: turns the findings into a plan. The buttons switch between what happens if nothing is done, using a slider to move forward in time, and a ranked list of fixes where a slider shifts the priority from what is most urgent to what protects the most equipment. The dataset contains hourly monitoring from 10 SQL databases on Azure at 7 sites, from 1 August to 16 September 2026. Each database is measured on 8 metrics, such as CPU, memory, disk load and blocked sessions, and each metric has a warning limit and a critical limit. The dataset also includes the value of the equipment that depends on each system, which sites and data feeds the systems share, and results from regular health checks. The finals was an unforgettable experience and i'm grateful for all that the inspiration this forum has brought me😄 Please feel free to connect on linkedin: www.linkedin.com/in/mariusjhellePitchside Pro: No One Plays on One Foot
At the core of this submission is a single idea: One. One analysis, one story, one human truth. From the outset, the question was clear—what drives Pitchside Pro's revenue, and what should we do next? The expected response would be to isolate drivers and present recommendations. Instead, I chose to unify them. The analysis revealed that while traffic and orders matter, customers—the fans—are the true driver of growth. This became the anchor: in e-commerce, marketing, and football, outcomes are never individual. People buy from people. No one plays on one foot. The report is built as a journey—from activation to belonging to identity—where data and psychology move together. Each page answers the business question while uncovering the human behavior behind it: how action builds momentum, how belonging reinforces growth, and how identity forms through what customers choose. But insight alone isn’t enough for executives. They care about action. So I extended the analysis into a campaign—connecting Problem → Data → Solution—so that every recommendation is not just defensible, but executable. This is why the narrative doesn’t stop at “what is happening,” but leads directly into “what should we do next.” Technically, the solution stays grounded and intentional. I used Power BI’s native visuals throughout, ensuring clarity, performance, and trust—supplemented only by HTML for the video experience. Accessibility was treated as a core requirement: leveraging Power BI's Accessible City Park theme, clear font hierarchy, structured tab order, descriptive alt text, and purposeful tooltips to support different ways of interacting with the report. To further extend accessibility and learning, I created a guided video walkthrough that can be accessed through the landing page, and for the campaign teaser in the last page, I leveraged Gen AI to bring the story to life—recognizing that insight is most powerful when it can be experienced, not just read. This work is both personal and collective. It stands on the shoulders of giants—drawing inspiration from practitioners like Paulo Grijo, Gus Bavia, Elena Drakulevska, and Shannon Lindsay slindsay —and shaped by the encouragement of my supportive and awesome mentees in the Power BI Community (my sincerest gratitude to you all!) As a data mentor, I approached this challenge as an opportunity to teach, because I believe the best way to learn is to explain and to model. In the end, this submission reflects how I think about data: not as isolated metrics, but as something that connects people, decisions, and action. And when everything aligns—analysis, psychology, design, and execution—we don’t just explain performance… we move it, we grow it, together, as one. -Jerome Ian Arbonida eyJrIjoiMTBhMWU2YTctYzAyZC00OGU5LTliZjMtMDFmNTUyOGE3MTgxIiwidCI6ImJkMDNhNzM1LTJhYTMtNGNjYS05NzIyLTJhZTQ5MjlhYjNlYyIsImMiOjEwfQ%3D%3D
Lego Data Museum - World Champs BCN 26 - Round 2 - Richard Ampie
This one was fun. For the Power BI DataViz World Championship I turned the Rebrickable LEGO database into a small data museum — four halls, one guide who walks you through all of them. The Grand Hall: your ticket, the key takeaway, and the doors to everything else. The History: 77 years of LEGO on a single gold curve, with an evidence vault backing every claim. The Sanctuary: a floating gallery of the landmark builds, like the drivable million-piece Bugatti. Beyond the Bricks: parks, films, the fans' designs… and an arcade room with playable LEGO-inspired games, right inside the report. I learned a lot building it: about the data, and about how far a canvas can stretch when you stop treating it like a dashboard. eyJrIjoiYmMxY2Y0NDAtZDhkNy00Y2Y1LWIyOGItOTU1MjY3NGVjMWJlIiwidCI6IjE5Y2VmZmU2LWEzNWUtNGY2Mi1hZDU5LTZkMGQwYTFiNGE3ZCIsImMiOjZ9PitchSide Pro - The Story Behind the Sales
Hi, The challenge was making one report do three jobs at once: clear at a glance, deep on demand, and usable every day. I tried to cover all - each page gives you the overview first, and then there are filters and drilldowns if you want to go deeper or look at a specific day. To keep that interactivity real, I made sure at least 50% of the visuals on each page are native - so the report isn't just nice to look at, it's genuinely explorable. Pages: Home - Daily top-line: where we stand today vs last year, the 30-day trend, and today's orders and products. The Calendar - What moves revenue: event types vs a normal day, with product mix, discount cost and clear actions. Products - What sells: Pareto concentration, profitability, bundles and discount reliance - each with a scale/protect/prune/grow verdict. Segments - Who our customers are: core profiles vs profiles worth chasing, plus a What-If on the growth prize. Channel - Where traffic comes from: the Web vs App funnel and a What-If showing conversion beats buying more traffic. Throughout, the clean overview sits on top while tables, matrices and toggled views let you drill down - from category to product, region to country, channel to source - so it works for a daily glance and a deeper dig alike. All illustrations generated with chatgpt. Would love to get the opportunity to show more of what I can do on stage in Barcelona! 🇪🇸 Thanks for taking a look, Marius I’ve also recently joined LinkedIn, so feel free to connect with me here! www.linkedin.com/in/mariusjhelle eyJrIjoiY2U5ODhmM2YtYWEyMy00MzU5LTk5MTQtZTE2N2ZlZTgxNTc0IiwidCI6ImI2ZGEwOTc1LTEwY2EtNDE0ZS04YTZjLTE1ZjgzMzgxZGUzMiJ9True Colors · World Champs BCN
TRUE COLORS · 75 years of LEGO, one color at a time Back for my second run at this championship — and this time I wanted to tell a real story, not just build charts. 📈 So here it is: LEGO's palette as what it actually is, a business story. From 3 colors in 1950 to 113 in 2004 — right as the company nearly went bankrupt — and then a purge that wiped out dozens in three years. Today the rainbow is wider than ever, yet half of every brick is still black, white or gray. A bit of what's under the hood, for the curious: official Rebrickable data, a model stitched together with Power Query and DAX, and three little Deneb (Vega-Lite) pieces I'm proud of — the 273-bar barcode that breathes when you hover, the purge graveyard, and the neutral waffle. The idea that guided the whole thing: a toy deserves a report you can actually play with. It tells the story on its own if you just read it, but there's twice as much waiting if you start clicking. And I cared about accessibility for real, not as a box to tick: alt text everywhere (some of it dynamic — the brick card literally narrates itself), reading order that matches how your eye moves, contrast checked properly and measured (up to 16:1 on the main ink), grays you can tell apart by lightness and not just hue, and a searchable table in the epilogue as a text fallback. Full disclosure: I finished this in the small hours, jumping around my living room, because Spain just won the World Cup! ⚽ If the file opens a little euphoric tonight, well… now you know why. Thanks for reading, and for having me back. 🏆 eyJrIjoiOTZmMTk5MzEtMDkwMi00NDE4LWJmYTYtZWU4MmMzMWM0Yjc5IiwidCI6IjhiNzFhMjJkLTU2MmMtNGQyZi04YjFhLWNmMzAwNDE1NjgzOCIsImMiOjl9&pageName=8546b9c3df6e86334a31
