📊 Analyst Forge: A 30-Day Self-Driven Data Analyst Challenge Using Python, Jupyter & Power BI

👋 Introduction

In a world where everyone wants to “learn data,” I decided to stop browsing tutorials and forge my own path. I created a personal 30-day challenge called Analyst Forge, a structured system to practice real data thinking every day using Python, Jupyter Notebooks, and Power BI.

In this post, I’ll walk you through the project structure, learning methodology, tools used, and how I turned this into a skill-building journey — and a step toward becoming internship-ready.

📁 Folder Structure and Workflow

Each day of the challenge was contained in a clearly labeled folder like 01, 02, and so on. Here’s what every question folder typically included:

*_question.ipynb – A Jupyter Notebook with the full problem and solution
Notes.md – My written explanation (answers), thought process, insights, mistakes, and learnings
Dataset files – CSV or Excel files (real or simulated) used in the analysis
(Optional): valuable_insights.md or .pbix files for Power BI dashboards

Additionally, outside the question folders, I maintained:

A general formulas sheet (Markdown) for reusable tricks and logic
A requirements.txt file for reproducibility
A README.md summarizing the challenge, tools, and reflections

🧠 Learning Model

I used ChatGPT as a virtual mentor throughout this journey. Each day, it would:

Give me a problem (sometimes based on real-world framing)
Ask for my insights
Grade me strictly on a scale of 1–10
Offer visualization hints or code suggestions to guide learning
Encourage me to reflect on why my interpretation made sense or failed

No Stack Overflow. No copying. Just raw thinking and daily practice.

🧩 Tools Used

Python: pandas, seaborn, matplotlib, NumPy
Jupyter Notebook: for flexible experimentation
Power BI: for visual summaries and business framing
Markdown (Notes.md): to document insights, learnings, and mistakes

🔍 Reflection

What was my biggest improvement across the 30 days?

I learned how to read and interpret data more confidently. While I sometimes looked up or cheated for code or insights, repetition and practice helped me understand what the code was doing. I also learned how to plot data effectively, make graphs visually appealing, and explore different data types, including time series.

How did my thinking shift from Day 1 to Day 30?

On Day 1, I wasn’t sure where to start. By Day 30, I could explore and interpret datasets quickly. Some insights felt repetitive due to demo data, but that taught me a real-world lesson: asking better questions matters more than finding flashy results.

What would I include in my analyst portfolio to show growth?

I’d include the insights I wrote, the visualizations I created, and the ability to explain data clearly — not just code.

🧭 How I Structured the Challenge

This wasn’t random problem-solving — I followed a three-phase plan to gradually build my abilities:

Phase 1: Logic, math puzzles, and clean intuition. No libraries, just thinking.
Phase 2: Medium-to-hard analysis problems with real/synthetic datasets. I used Python and Power BI, but avoided reading documentation to push myself.
Phase 3: Real-world challenges requiring framing, storytelling, dashboards, and insight synthesis — mimicking what analysts do in businesses.

From Day 11 onward, each challenge also had:

A title explaining the core concept
A dataset or schema to simulate a real environment
A main task to trigger analytical thinking
Mild coding suggestions (not solutions)
Optional Power BI/reporting angle
A soft reminder of what I should submit or reflect on

✨ Start Your Own Analyst Forge

Want to build your data reading intuition and analytical muscle like I did?

Here’s the exact prompt I gave to ChatGPT to launch my challenge. You can copy and customize it to suit your needs:

I am a learning AI/ML enthusiast and unfortunately don’t have any real data reading capabilities.

So now I want to change this and build a strong data analyst persona.  
Be my teacher and give me a question every day for 30 days.

Each question should be medium to hard, and focus on reading, interpreting, and extracting insights from data.  
Also, give me a strict score out of 10 for each solution.

Add a visual hint or a graph suggestion each time — because I want to learn how to read and also represent the data.

I’ll be using Python libraries and Power BI throughout this challenge.  
Please be honest and do not repeat questions.

And later, I refined it into this structured mentorship model:

You are my mentor and guide for a 30-day self-designed Analyst Forge Challenge that I created to build my analytical thinking, problem-solving, and data interpretation skills using Python and Power BI.

The challenge is broken into 3 phases:

- Phase 1: Logical thinking, math-based problems, intuition puzzles — minimal data structure, just clean logical rigor.
- Phase 2: Daily medium-to-hard data analyst problems testing data reasoning, visualizations, Python analysis (without docs), and Power BI.
- Phase 3: Applied creativity — solving real-world framed problems, combining skills across storytelling, dashboards, visualization, and framing business problems.

I want each challenge to have:
1. A clear title describing the core concept it teaches (especially from Day 11 onward).
2. A dataset (real or synthetic) or a description of what I should create.
3. A core problem statement or task that forces me to apply **thinking**, not just coding.
4. A mild suggestion for how to begin coding.
5. An optional Power BI angle or storytelling framing.
6. A soft reminder to reflect or submit my insights.

👨‍🏫 My Mentor

I used ChatGPT as my mentor for all 30 days.
It guided, challenged, and evaluated me without hand-holding — making this the most focused learning I’ve ever done.

🔗 Want to Explore It?

🧱 GitHub Repo: Analyst Forge

Explore the full structure, notebooks, notes, and insights in the repo.

📌 Final Thought

“Forging insight one dataset at a time.”

This project wasn’t just about Python or Power BI — it was about learning to think like a data analyst.
And that mindset is something I’ll carry forward to every project and opportunity that comes next.

Search This Blog

My Commit Log