Skip to content

Latest commit

Β 

History

27 Commits

Folders and files

NameName
Last commit message
Last commit date
Β 
Β 

Repository files navigation

30 Days. 30 Problems. 30 Business Solutions.

Introduction

30 Day Applied Business Strategy Challenge is a personal initiative where I solve one real world business problem every day for thirty days.
The goal is not to write code for the sake of code. The goal is to think like someone who belongs inside a strong team, someone who can take an ambiguous problem, understand the business impact, design a structured approach, and deliver a usable solution.


πŸ“‚ Project Gallery

Day 1
Day 1
Project Link
Day 2
Day 2
Project Link
Day 3
Day 3
Project Link
Day 4
Day 4
Project Link
Day 5
Day 5
Project Link
Day 6
Day 6
Project Link
Day 7
Day 7
Week 1 Reflection
Day 8
Day 8
Project Link
Day 9
Day 9
Project Link
Day 10
Day 10
Project Link
Day 11
Day 11
Post
Day 12
Day 12
Project Link
Day 13
Day 13
Project Link
Day 14
Day 14
Post
Day 15
Day 15
Project Link
Day 16
Day 13
Project Link
Day 17
Day 17
Project Link
Day 18
Day 17
Project Link
Day 19
Day 13
Project Link
Day 20
Day 20
Project Link
Day 21
Day 21
Post
Day 22
Day 22
Project Link
Day 23
Day 23
Project Link
Day 24
Day 24
Post
Day 25
Day 25
Day 26
Day 26
Project Link
Day 27
Day 26
Project Link
Day 28
Day 28
Post Link
Day 29
Day 29
Post Link
Day 30
Day 30
Post Link

🌟 This challenge brings together the skills I care about most:

  • problem solving
  • strategic thinking
  • project management
  • clear communication
  • data driven validation
  • continuous learning
    Every problem I pick reflects the kind of challenge that real teams face across fintech, consulting, operations, strategy, and product management.

🌟 Each day follows the same core structure:

  • What is the business problem
  • Why does it matter
  • Who does it impact
  • What questions do we need to answer
  • What approach makes sense
  • What is the outcome or recommendation

Some solutions require analytics.
Some require reasoning, planning, prioritisation, or risk assessment.
Some require forecasting or modelling.
Some require creating a process that teams can follow.

The focus is not on the tool, but on the thinking behind the solution. My goal is to become the type of person who does not wait for instructions, but who takes initiative, breaks down complexity, and adds clarity wherever something is unclear. At the end of thirty days, I want a portfolio that shows not just technical skills, but judgment, reasoning, and the ability to solve problems that actually matter to a business.

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors