Problem Identification Lab Program

Problem Identification Lab

Powered by the Memorial Centre for Entrepreneurship (MCE)
In collaboration with the Engineering Co‑op Office

Turn workplace challenges into opportunities.

The Problem Identification Lab helps engineering co-op students capture high-quality, industry-rooted problem statements and then transform them with guidance.  

Problem identification is a core engineering skill because real‑world challenges aren’t clearly defined—engineers must first understand what’s actually wrong. By identifying the right problem, they can make better decisions, reduce wasted effort, and develop solutions that have real impact.

The Problem Identification Lab builds a continuous pipeline of high-quality, industry-informed problems gathered directly from students working in the field.  These problem statements form the MCE Problem Bank, a shared resource for new startup ideas grounded in real market needs.

What Are The Benefits?

Each term, top problem statements are showcased at our end‑of‑term celebration and mixer, with a chance to receive $250 in recognition—plus the opportunity to meet other like‑minded builders, mentors, and alumni.

What Makes a Strong Problem Submission?

A great problem statement is:

  • Clear: easy for anyone to understand
  • Specific: focused on a single, well-defined issue
  • Impactful: affects workflow, cost, safety, efficiency, or productivity
  • Authentic: based on your real co‑op experience
  • Non‑confidential: does not reveal proprietary or restricted information

You don’t need to brainstorm solutions—just explain the problem and its significance.

Who Can Participate?

This program is open to:

  • Engineering students currently completing a Memorial University co‑op work term
  • Students in any industry or sector

Ready to Submit a Problem?

Submit Your Problem Here 

What’s a Problem Statement?

A problem statement is a clear and concise description of an issue that needs to be solved. It helps define what the problem is, who it affects, and why it matters. A strong problem statement does not jump to solutions. Instead, it outlines the current situation and the gap between what is happening and what should be happening.

Here are some examples of Problem Statements in various industries:
CoLab Software as an example: Engineering teams often struggle to review complex designs because feedback is scattered across tools and people, making it hard to track decisions. This leads to miscommunication, missed issues, and slower product development.

Engineering design review problem

  • Feedback scattered across meetings, emails, and slide decks
  • Limited access to full design context during reviews
  • Difficult to track decisions and changes over time
  • Knowledge often lives in individuals, not shared systems
  • Leads to:
    • Miscommunication and misunderstandings
    • Missed design issues and costly rework
    • Slower product development timelines
    • Loss of institutional knowledge

BreatheSuite as an example: Patients with chronic respiratory conditions often struggle to use inhalers correctly and manage their care without ongoing support. This leads to poor disease control, ineffective treatment, and increased healthcare use.

Respiratory care adherence problem

  • High rates of incorrect inhaler usage
  • Limited patient understanding of technique and triggers
  • Lack of continuous monitoring and support at home
  • Care often dependent on infrequent clinical visits
  • Leads to:
    • Poor disease control and symptom flare‑ups
    • Reduced effectiveness of medication
    • Increased hospital visits and healthcare costs
    • Lower quality of life for patients

Confidentiality

Submitting only non‑confidential information helps ensure that no sensitive details from an employer or organization are disclosed. Instead of referencing specific companies, products, or internal processes, students are encouraged to frame their submissions around broader, widely applicable problems. For example, rather than naming a company, a student might describe “challenges with coordinating communication across distributed engineering teams.” This approach protects confidentiality while still allowing students to clearly demonstrate their understanding of real‑world issues and develop problem identification skills that apply across industries.

Questions?

Email MCE at: mce@mun.ca
Visit us at: ENG-3075