<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Mary Ngure</title>
    <description>The latest articles on DEV Community by Mary Ngure (@maryngure).</description>
    <link>https://dev.to/maryngure</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3969345%2F32a26aa6-9695-47e3-9ac8-47185ebc045b.png</url>
      <title>DEV Community: Mary Ngure</title>
      <link>https://dev.to/maryngure</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/maryngure"/>
    <language>en</language>
    <item>
      <title>PowerBI; Relationships, Schemas &amp; Dashboards</title>
      <dc:creator>Mary Ngure</dc:creator>
      <pubDate>Mon, 29 Jun 2026 06:06:38 +0000</pubDate>
      <link>https://dev.to/maryngure/powerbi-relationships-schemas-dashboards-28jo</link>
      <guid>https://dev.to/maryngure/powerbi-relationships-schemas-dashboards-28jo</guid>
      <description>&lt;p&gt;When I started learning Power BI, I thought dashboards were mostly about choosing the right charts.&lt;/p&gt;

&lt;p&gt;Then I discovered data modeling.&lt;/p&gt;

&lt;p&gt;Everything clicked.&lt;/p&gt;

&lt;p&gt;I realized that dashboards aren't powered by visuals, they're powered by relationships.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Mistake I Used to Make
&lt;/h2&gt;

&lt;p&gt;Coming from Excel, I was used to keeping everything in one large table.&lt;/p&gt;

&lt;p&gt;It worked... until the data became larger and more complex.&lt;/p&gt;

&lt;p&gt;Duplicate information increased.&lt;/p&gt;

&lt;p&gt;Performance slowed down.&lt;/p&gt;

&lt;p&gt;And maintaining the dataset became frustrating.&lt;/p&gt;

&lt;p&gt;Power BI introduced me to a completely different way of thinking.&lt;/p&gt;

&lt;p&gt;Instead of one giant spreadsheet, data is organized into related tables.&lt;/p&gt;

&lt;h2&gt;
  
  
  Understanding Relationships
&lt;/h2&gt;

&lt;p&gt;Relationships allow tables to communicate using common fields, often called keys.&lt;/p&gt;

&lt;p&gt;For example:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A Sales table stores transactions.&lt;/li&gt;
&lt;li&gt;A Products table stores product information.&lt;/li&gt;
&lt;li&gt;A Customers table stores customer details.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Rather than repeating product names thousands of times, Power BI connects the tables using Product IDs.&lt;/p&gt;

&lt;p&gt;This keeps the model cleaner, faster, and easier to maintain.&lt;/p&gt;

&lt;h2&gt;
  
  
  Discovering Star Schema
&lt;/h2&gt;

&lt;p&gt;One concept that completely changed my understanding was the Star Schema.&lt;/p&gt;

&lt;p&gt;Instead of random tables connected everywhere, the model is organized into:&lt;/p&gt;

&lt;h3&gt;
  
  
  Fact Table
&lt;/h3&gt;

&lt;p&gt;Contains measurable business events such as:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Sales&lt;/li&gt;
&lt;li&gt;Revenue&lt;/li&gt;
&lt;li&gt;Quantity Sold&lt;/li&gt;
&lt;li&gt;Profit&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Dimension Tables
&lt;/h3&gt;

&lt;p&gt;Contain descriptive information like:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Customers&lt;/li&gt;
&lt;li&gt;Products&lt;/li&gt;
&lt;li&gt;Locations&lt;/li&gt;
&lt;li&gt;Dates&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The fact table sits in the center, while the dimension tables surround it—forming a star.&lt;/p&gt;

&lt;p&gt;It's surprisingly elegant.&lt;/p&gt;

&lt;p&gt;And it's one of the reasons Power BI performs so efficiently.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Good Models Create Better Dashboards
&lt;/h2&gt;

&lt;p&gt;Once relationships were configured correctly, dashboard creation became much easier.&lt;/p&gt;

&lt;p&gt;Instead of manually combining data for every visual, Power BI automatically understood how everything connected.&lt;/p&gt;

&lt;p&gt;Slicers filtered multiple visuals correctly.&lt;/p&gt;

&lt;p&gt;Measures returned accurate results.&lt;/p&gt;

&lt;p&gt;Cross-filtering worked naturally.&lt;/p&gt;

&lt;p&gt;It felt like the model was doing half the work for me.&lt;/p&gt;

&lt;h2&gt;
  
  
  Dashboard Design Is More Than Pretty Colors
&lt;/h2&gt;

&lt;p&gt;Building dashboards taught me another important lesson.&lt;/p&gt;

&lt;p&gt;A dashboard isn't a decoration.&lt;/p&gt;

&lt;p&gt;It's a decision-making tool.&lt;/p&gt;

&lt;p&gt;Now, whenever I design one, I ask:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;What question should this answer?&lt;/li&gt;
&lt;li&gt;What KPI matters most?&lt;/li&gt;
&lt;li&gt;What action should someone take after seeing this visual?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Those questions have become more important than choosing between a bar chart or a line chart.&lt;/p&gt;

&lt;h2&gt;
  
  
  My Growing Power BI Workflow
&lt;/h2&gt;

&lt;p&gt;As I continue learning, my process has become surprisingly consistent:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Understand the business problem.&lt;/li&gt;
&lt;li&gt;Clean the data.&lt;/li&gt;
&lt;li&gt;Build relationships.&lt;/li&gt;
&lt;li&gt;Design a star schema.&lt;/li&gt;
&lt;li&gt;Create measures.&lt;/li&gt;
&lt;li&gt;Build visuals.&lt;/li&gt;
&lt;li&gt;Refine the dashboard until it tells a clear story.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Each step builds on the previous one.&lt;/p&gt;

&lt;p&gt;Skipping one almost always creates problems later.&lt;/p&gt;

&lt;h2&gt;
  
  
  Final Thoughts
&lt;/h2&gt;

&lt;p&gt;Power BI has taught me that great dashboards aren't created in the report view.&lt;/p&gt;

&lt;p&gt;They're created through thoughtful data modeling.&lt;/p&gt;

&lt;p&gt;The visuals may be what users notice first, but relationships are what make those visuals meaningful.&lt;/p&gt;

&lt;p&gt;I'm still learning, but every project reinforces the same lesson:&lt;/p&gt;

&lt;p&gt;Clean data is important.&lt;/p&gt;

&lt;p&gt;Well-designed models are powerful.&lt;/p&gt;

&lt;p&gt;And dashboards are simply the final chapter of a much bigger story.&lt;/p&gt;

</description>
      <category>analytics</category>
      <category>beginners</category>
      <category>data</category>
      <category>microsoft</category>
    </item>
    <item>
      <title>Learning Power BI; Where it all begins</title>
      <dc:creator>Mary Ngure</dc:creator>
      <pubDate>Mon, 29 Jun 2026 05:59:39 +0000</pubDate>
      <link>https://dev.to/maryngure/learning-power-bi-where-it-all-begins-5b5e</link>
      <guid>https://dev.to/maryngure/learning-power-bi-where-it-all-begins-5b5e</guid>
      <description>&lt;p&gt;When I first opened Power BI, I thought the exciting part would be building beautiful dashboards.&amp;nbsp;I was wrong. It is such a powerful tool.&lt;/p&gt;

&lt;p&gt;The real work and arguably the most important work starts long before creating charts. It starts with messy data.&lt;/p&gt;

&lt;p&gt;As someone transitioning deeper into data analytics, I've realized that data cleaning isn't the boring step people make it out to be. It's where you develop the mindset of an analyst. Every duplicate, missing value, incorrect data type, or inconsistent entry tells a story about the quality of your data.&lt;/p&gt;

&lt;p&gt;And if the data is wrong, your dashboard will simply visualize bad decisions.&lt;/p&gt;

&lt;h2&gt;
  
  
  My First Encounter with Power Query
&lt;/h2&gt;

&lt;p&gt;The first thing that surprised me was that Power BI separates data preparation from visualization through &lt;strong&gt;Power Query&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;Instead of editing the original dataset, Power Query records every transformation as a reusable step. This means that when new data is added later, I don't have to repeat the cleaning process manually.&lt;/p&gt;

&lt;p&gt;That alone completely changed how I thought about data preparation.&lt;/p&gt;

&lt;h2&gt;
  
  
  Cleaning Data Isn't Just Removing Errors
&lt;/h2&gt;

&lt;p&gt;One lesson I quickly learned is that cleaning data is about making it analysis-ready.&lt;/p&gt;

&lt;p&gt;Some of the common tasks I performed included:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Removing duplicate records&lt;/li&gt;
&lt;li&gt;Changing incorrect data types&lt;/li&gt;
&lt;li&gt;Renaming columns for clarity&lt;/li&gt;
&lt;li&gt;Replacing missing values&lt;/li&gt;
&lt;li&gt;Splitting and merging columns&lt;/li&gt;
&lt;li&gt;Creating calculated columns&lt;/li&gt;
&lt;li&gt;Filtering unnecessary rows&lt;/li&gt;
&lt;li&gt;Standardizing inconsistent text values&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Each transformation made the dataset a little more trustworthy.&lt;/p&gt;

&lt;h2&gt;
  
  
  Functions That Made My Life Easier
&lt;/h2&gt;

&lt;p&gt;As I continued practicing, I became more comfortable using functions inside Power Query.&lt;/p&gt;

&lt;p&gt;Some of my favorites include:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Text functions for cleaning inconsistent names&lt;/li&gt;
&lt;li&gt;Date functions for extracting months and years&lt;/li&gt;
&lt;li&gt;Conditional Columns for categorizing records&lt;/li&gt;
&lt;li&gt;Replace Values for fixing repeated errors&lt;/li&gt;
&lt;li&gt;Group By for summarizing data quickly&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;These small tools eliminated hours of manual work.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Biggest Lesson
&lt;/h2&gt;

&lt;p&gt;Before learning Power BI, I assumed analysts spent most of their time creating reports.&lt;/p&gt;

&lt;p&gt;Now I know that a significant portion of analytics happens before a single chart is built.&lt;/p&gt;

&lt;p&gt;Clean data creates confidence.&lt;/p&gt;

&lt;p&gt;Confidence creates better decisions.&lt;/p&gt;

&lt;h2&gt;
  
  
  What's Next?
&lt;/h2&gt;

&lt;p&gt;Now that I'm becoming comfortable cleaning data, I'm moving into one of the most interesting parts of Power BI, building relationships between tables and designing dashboards that tell meaningful stories instead of simply displaying numbers.&lt;/p&gt;

&lt;p&gt;Because data isn't valuable until someone can understand it.&lt;/p&gt;

&lt;p&gt;And that's exactly where Power BI starts to shine.&lt;/p&gt;




</description>
      <category>analytics</category>
      <category>beginners</category>
      <category>data</category>
      <category>learning</category>
    </item>
    <item>
      <title>How Excel is used in Real World Data Analysis</title>
      <dc:creator>Mary Ngure</dc:creator>
      <pubDate>Sun, 07 Jun 2026 08:05:09 +0000</pubDate>
      <link>https://dev.to/maryngure/how-excel-is-used-in-real-world-data-analysis-2lh3</link>
      <guid>https://dev.to/maryngure/how-excel-is-used-in-real-world-data-analysis-2lh3</guid>
      <description>&lt;p&gt;I’ve always  known  Excel as a tool for creating tables and performing simple calculations. However, after spending a week learning its fundamentals, I now understand why Excel remains one of the most widely used tools in data analysis.&lt;br&gt;
Microsoft Excel is a spreadsheet application that allows users to collect, organize, clean, analyze, calculate, and visualize data. Its user-friendly interface and powerful features make it a valuable tool for individuals and organizations across different industries.&lt;br&gt;
One way Excel is used in real-world data analysis is in business decision-making. Companies collect large amounts of data on sales, customers, and operations. Analysts use Excel to sort and filter this data, helping managers identify trends, monitor performance, and make informed decisions. For example, a retail business can sort products by sales volume to identify its best-selling items.&lt;br&gt;
Excel is also widely used in financial reporting. Businesses use it to track expenses, calculate profits, prepare budgets, and generate financial reports. With formulas and formatting tools, financial data can be organized in a way that is easy to understand and analyze.&lt;br&gt;
Another common application is marketing performance analysis. Marketing teams collect data from campaigns, websites, and social media platforms. Excel can be used to analyze campaign results, compare performance metrics, and identify which strategies are generating the best outcomes.&lt;br&gt;
Throughout this week, I learned several Excel features and formulas that are useful in data analysis. The first is filtering, which allows analysts to display only the data that meets specific criteria. This is useful when working with large datasets and looking for particular information. I also learned about data validation, which helps maintain data quality by restricting the type of information users can enter into cells. This reduces errors and improves data accuracy.&lt;br&gt;
In addition, I learned functions such as SUM(), AVERAGE(), and COUNT(). SUM() helps calculate totals, AVERAGE() finds the mean value of a dataset, and COUNT() determines how many numerical values exist within a range. These functions make it easier to summarize and understand data quickly. I also found text functions such as TRIM() and PROPER() useful for cleaning and standardizing data before analysis.&lt;br&gt;
Learning Excel has changed the way I see data. Before, I saw data as a collection of numbers and text. Now, I see it as information that can tell a story and support decision-making when properly organized and analyzed. Excel has shown me that effective data analysis begins with understanding how to clean, structure, and explore data. As I continue my journey in data science, I can already see how these foundational Excel skills will support my learning of more advanced tools and techniques.&lt;/p&gt;

</description>
      <category>analytics</category>
      <category>beginners</category>
      <category>datascience</category>
      <category>microsoft</category>
    </item>
  </channel>
</rss>
