From Problem to Project: How to Build Support for Your Initiative by Starting with the Right Question

As an intern, you're in a unique position to see your workplace with fresh eyes. While this outsider perspective can sometimes feel isolating, it's actually your secret weapon for making meaningful contributions. The key isn't jumping straight to solutions—it's learning to identify problems worth solving and building the support you need to tackle them.

Start by Becoming a Problem Detective

Your first few weeks as an intern are gold for problem identification. You're asking "why do we do it this way?" while everyone else has accepted the status quo. Instead of dismissing these moments of confusion, start documenting them.

Keep a simple log of friction points you observe: processes that seem unnecessarily complicated, information that's hard to find, tasks that multiple people duplicate, or workflows that frequently break down. Don't judge these observations yet—just collect them.

The magic happens when you start noticing patterns. Maybe three different people have complained about the same reporting process this week. Perhaps you've watched two separate teams recreate similar resources because they didn't know the other existed. These patterns often point to problems that others feel but haven't articulated.

Craft a Problem Statement That Resonates

Once you've identified a potential problem, resist the urge to immediately propose a solution. Instead, invest time in understanding and articulating the problem clearly. A strong problem statement should answer three questions:

• What is happening? Describe the current situation objectively, without editorial comments.

• Why does this matter? Connect the problem to outcomes people care about.

• Who is affected? Identify the stakeholders who feel this pain.

Here are two examples of strong problem statements:

Example 1: Information Access Problem

What is happening? New team members spend their first two weeks repeatedly asking the same questions about project protocols, client preferences, and internal tools because this information exists in scattered emails, outdated wiki pages, and individual team members' heads.

Why does this matter? This creates a productivity drain where experienced team members interrupt their work 8–10 times per day to answer routine questions, while new people feel hesitant to keep asking and often make avoidable mistakes due to incomplete information.

Who is affected? Every new hire (we've onboarded 4 people in the past 3 months), the 6 senior team members who field most questions, and project timelines that get delayed when new team members work with outdated information.

Example 2: Process Efficiency Problem

What is happening? Our team creates client presentation decks by manually copying data from three different systems (CRM, analytics dashboard, and project management tool), then reformatting and double-checking the numbers, which takes 2–3 hours per deck.

Why does this matter? We create 12–15 client decks monthly, meaning we spend 30+ hours on data transfer and formatting instead of analysis and strategy work. Plus, manual copying introduces errors that require additional review cycles and sometimes embarrassing corrections.

Who is affected? The 4 account managers who build these decks work late to accommodate the time-intensive process, analysts can't focus on higher-value work, and clients occasionally receive incorrect data that undermines our credibility.

The best problem statements feel obvious once you read them, but weren't obvious before someone took the time to write them down clearly.

Test Your Problem Statement Before You Fall in Love With It

Here's where many well-intentioned interns stumble: they become attached to their problem statement before validating it with others. Your fresh perspective is valuable, but you might be missing context about why things work the way they do.

Start small and informal. Using the first example above, you might say to your manager:

"I noticed new team members ask similar questions repeatedly during their first weeks. Is that something that bothers other people too, or am I missing something about how our onboarding process is supposed to work?"

This approach serves multiple purposes. You're gathering information about whether others share your perception. You're learning about previous attempts to address this issue. Most importantly, you're beginning to build awareness of the problem without positioning yourself as the critic who's here to fix everything.

Listen carefully to the responses. If someone says, "oh, we've tried to fix that before but it's complicated because..." you've just learned valuable context that will make any eventual solution much stronger.

Build a Coalition Around the Problem

Once you've confirmed that others recognize the problem, start expanding the conversation strategically. The goal isn't to complain or criticize—it's to build shared understanding about an opportunity for improvement.

When you bring up the problem in conversations, focus on gathering perspectives rather than advocating for your viewpoint. Ask questions like:

"How do you work around this issue?""What would need to be different for this process to work smoothly?"

These questions help others articulate their own frustrations and start envisioning what better might look like.

Pay attention to who seems most engaged by the problem discussion. These people will become your allies when you're ready to propose solutions. They're also the ones most likely to provide helpful input as you develop your approach.

Document these conversations in your notes. You're building a case not just for the problem's existence, but for why solving it matters to people whose opinions carry weight in your organization.

Don’t Stop at One: Identify and Prioritize the Right Problems to Solve

Before you jump into pitching a project, take time to step back and view the bigger picture. Instead of focusing on a single issue, use your first few weeks to observe and record a variety of problems—large and small. Think of it as your internal discovery period.

Once you've collected a healthy set of potential problems, evaluate them against key criteria such as:

• Strategic importance: Does this problem impact a key goal or priority of the team or organization?

• Customer or user impact: Would solving this create a noticeably better experience?

• Financial implications: Could addressing this save time, money, or resources?

• Feasibility: Is the problem solvable within the scope of your time, access, and role?

After that review, identify the top one—or a small handful—of problems that are worth moving forward. Not everything will make the cut, and that’s okay. Prioritization is part of showing leadership.

When you present your idea, you can say:

“I spent some time observing and comparing several opportunities for improvement. Based on impact and alignment with our goals, I believe this one has the most potential to make a difference.”

This kind of thoughtful framing makes your initiative harder to dismiss—and easier to support.

Transition from Problem to Solution Ownership

Here's where initiative really shines: once you've established that a problem is real and worth solving, you can position yourself as the person to address it. But notice the sequence—you've built credibility by doing the analytical work first, gathering input from stakeholders, and demonstrating that you understand the complexity involved.

When you're ready to propose taking ownership of a solution, you can say something like:

"Based on our conversations about new team member onboarding challenges, I've been thinking about some approaches that might help. Would it be useful for me to spend some time researching options and putting together a proposal for how we might create a more structured information resource?"

This positions you as someone who listens, thinks strategically, and follows through—exactly the qualities that turn internships into job offers and strong professional relationships.

Make Your Project Proposal Irresistible

When you do propose a project to address your identified problem, you're building on a foundation of shared understanding. Your proposal can reference the conversations you've had and the insights you've gathered. You can acknowledge the constraints and complexities that stakeholders have mentioned. Most importantly, you can demonstrate that this project addresses a problem that matters to people other than just you.

A proposal built on this foundation sounds like:

"Several people have mentioned the challenges with our new team member onboarding process, and I'd like to propose a solution that addresses the main pain points you've all identified..."

…rather than:

"I think we should change how we onboard people because I have a better idea."

The difference is subtle but crucial. In the first case, you're positioned as someone who listens, analyzes, and builds consensus. In the second, you risk sounding like the intern who shows up and immediately wants to reorganize everything.

Conclusion: Build Your Reputation by Solving What Matters

Taking initiative this way requires patience, but it builds something far more valuable than just getting your project approved. You’re developing a reputation as someone who sees what others miss, listens well, and follows through with purpose.

This process—spotting problems, validating them with others, building coalitions, and proposing solutions rooted in real needs—isn’t just for internships. It’s the foundation of meaningful leadership.

Every conversation you initiate, every observation you document, and every small step toward change helps build muscles that will serve you for the rest of your career. It’s not about having all the answers; it’s about showing that you care enough to ask the right questions—and bold enough to act on what you find.

The problems you identify today may seem small, but learning how to transform them into supported, strategic projects is one of the most valuable skills you can develop.

What problem have you noticed lately that might be worth exploring more deeply? Who could you talk to this week to begin building a shared understanding around it?

---

Forward this post to a friend!

Not have a Sparks Mentor yet? The Sparks Mentorship Program is here to connect you with experienced mentors who can help guide your journey. Whether you need career advice, networking opportunities, resume tips, or just someone to offer insight and support, our mentors are ready to help. This is the kind of advice you could be getting—so why wait? Join today! Click the button to learn more and take the next step in your journey.

Learn More!