Proposal Writing & Problem-Solving: Structure, Analysis & Persuasion

Key Concepts and Structure of a Proposal

1. Definition and Purpose

A proposal is a formal document that presents a plan, solution, or request for approval (funding, resources, or support). It is problem-solving in writing, blending analysis, research, and persuasive communication.

Key Goals:

• Define a clear problem.
• Propose a solution with evidence.
• Persuade stakeholders (clients, committees, or managers) to approve it.

2. Types of Proposals

3. Core Components of a Proposal

Every proposal follows a logical structure to ensure clarity and persuasiveness. Below is a breakdown with a real-world example (a proposal for eSewa to improve its mobile app’s user experience).

A. Title Page

• Purpose: First impression; includes project name, submitter’s details, and date.
• Key Elements:
  • Project title (clear and concise).
  • Name, designation, and contact of the proposer.
  • Date of submission.
  • Recipient’s name/organization (if known).

Example (eSewa App Redesign Proposal):

eSewa Mobile App Redesign Proposal
Submitted by: [Your Name], UX Designer, TechHub Nepal
Date: [DD/MM/YYYY]
For: eSewa Management Team

B. Executive Summary (1 Page Max)

• Purpose: A mini-proposal—summarizes the entire document for busy readers.
• Key Elements:
  • Problem statement (1-2 sentences).
  • Proposed solution.
  • Expected benefits.
  • Budget (if applicable).
  • Timeline.

Example (eSewa):

"eSewa’s current mobile app has a 30% user dropout rate due to complex navigation and slow transaction processing. This proposal outlines a redesign focusing on intuitive UI/UX, faster load times, and biometric authentication. Expected outcomes: 20% increase in user retention, 15% faster transactions, and improved customer satisfaction. Budget: NPR 500,000. Timeline: 6 months."

C. Problem Statement

• Purpose: Clearly define the issue you are solving.
• How to Write It:
  • Use data (e.g., user surveys, analytics).
  • Avoid vague language (❌ "The app is slow" → ✅ "Transaction processing takes 4.2 seconds on average, exceeding the 2-second industry benchmark.").
  • Explain why it matters (impact on users, business, or society).

Example (eSewa):

"According to a recent survey of 5,000 eSewa users, 68% cited ‘difficulty navigating menus’ and ‘slow transaction confirmation’ as primary pain points. The current app’s average transaction time of 4.2 seconds (vs. competitors’ 1.8s) leads to a 25% abandonment rate during checkout, costing eSewa NPR 20 million annually in lost revenue."

D. Objectives

• Purpose: What you aim to achieve (SMART: Specific, Measurable, Achievable, Relevant, Time-bound).
• Example (eSewa):
  • Reduce transaction time to ≤2 seconds within 3 months.
  • Increase user retention rate by 20% in 6 months.
  • Achieve a Net Promoter Score (NPS) of 60+ post-redesign.

E. Methodology (How You’ll Solve the Problem)

• Purpose: Explain your approach with evidence.
• Key Sections:
  1. Research: User interviews, surveys, competitor analysis.
  2. Design Process: Wireframing, prototyping, usability testing.
  3. Tools/Technologies: Figma, Firebase, or existing eSewa backend APIs.
  4. Team Roles: Who will execute (e.g., UX designer, developers, QA testers).

Example (eSewa):

"Phase 1 (Month 1-2): Conduct 200 user interviews and analyze competitor apps (e.g., Khalti, IME Pay). Phase 2 (Month 3-4): Develop low-fidelity prototypes in Figma, test with 50 users, and refine based on feedback. Phase 3 (Month 5-6): Integrate biometric login with eSewa’s existing backend and roll out a beta version to 10% of users."

F. Work Plan (Timeline/Gantt Chart)

• Purpose: Show stakeholders when and how the project will progress.
• Format: Use a table or Gantt chart (Mermaid example below).

gantt
    title eSewa App Redesign Timeline
    dateFormat  MM-YY
    section Research
    User Interviews    :a1, 1, 01-23
    Competitor Analysis :a2, 1, 02-23
    section Design
    Wireframing        :b1, 2, 03-04
    Prototyping        :b2, 2, 05-06
    Usability Testing  :b3, 1, 07-23
    section Development
    Backend Integration :c1, 2, 08-09
    Beta Testing       :c2, 1, 10-23
    Full Launch        :c3, 1, 11-23

G. Budget

• Purpose: Justify costs and ensure financial feasibility.
• Example (eSewa):

  Item	Cost (NPR)	Notes
  User Research	50,000	200 interviews + surveys
  UX Design Tools	30,000	Figma license, cloud storage
  Developer Salaries	250,000	3 developers × 2 months
  Server Upgrades	100,000	Firebase scaling
  Contingency (10%)	50,000	Unforeseen expenses
  Total	530,000

H. Expected Outcomes & Benefits

• Quantitative: Metrics (e.g., "20% faster transactions").
• Qualitative: User satisfaction, brand reputation.
• Example (eSewa):
  • For Users: Faster payments, easier navigation.
  • For eSewa: Higher retention, reduced customer support costs.
  • For Nepal: More digital financial inclusion.

I. Risks & Mitigation

• Purpose: Show you’ve thought ahead.
• Example (eSewa):

  Risk	Mitigation Strategy
  Low user adoption of biometrics	Pilot test with 10% users first.
  Delay in backend integration	Assign a dedicated developer with eSewa API experience.
  Budget overruns	Track expenses weekly; use agile methodology.

J. Conclusion & Call to Action

• Purpose: End with a strong closing—what you want the reader to do.
• Example (eSewa):

  "This redesign will position eSewa as Nepal’s leading digital payment platform. We request approval to proceed with Phase 1 (research) by [date]. Please let us know if you require additional details or a meeting to discuss further."

4. Problem-Solving in Proposals

Proposals are not just documents—they solve problems. Here’s how to approach problem-solving:

A. Analyzing the Problem

1. Identify the Root Cause:
   • Ask: Why does this problem exist? (e.g., eSewa’s slow app → outdated backend + poor UI).
2. Gather Data:
   • Use quantitative (surveys, analytics) and qualitative (interviews) data.
3. Stakeholder Analysis:
   • Who is affected? (e.g., eSewa users, merchants, bank partners).

B. Proposing Solutions

• Be Creative but Feasible:
  • ✅ "Integrate biometric login" (feasible, aligns with eSewa’s security goals).
  • ❌ "Replace the entire app with a blockchain system" (too risky).
• Use the "5 Whys" Technique:
  • Why is the app slow? → Because of unoptimized code.
  • Why is the code unoptimized? → Because developers lack time for refactoring.
  • Solution: Allocate dedicated time for backend optimization.

C. Evaluating Solutions

Decision: Combine both—redesign UI + optimize backend in phases.

5. Ethical Considerations in Proposals

Technical writing requires transparency and integrity. Common ethical pitfalls:

• Plagiarism: Never copy-paste without citation.
• False Claims: Avoid exaggerated benefits (e.g., "This will 100% solve all problems").
• Bias: Present data objectively (e.g., if a feature fails in testing, state it).

Example of Ethical Writing (eSewa): ❌ "Our redesign will eliminate all user complaints." (Unrealistic) ✅ "Based on pilot tests, we expect a 30% reduction in complaints, though some legacy issues may persist."

6. Real-World Applications

A. eSewa: Digital Payment Optimization

• Problem: High user dropout due to slow transactions.
• Proposal Idea: Redesign app + backend optimization (as above).
• Why It Matters: Nepal’s digital economy relies on eSewa; faster payments = more trust.

B. Pathao: Electric Scooter Fleet Expansion

• Problem: Traffic congestion in Kathmandu increases delivery delays.
• Proposal Idea:
  • Partner with EV manufacturers (e.g., Hero Electric) for scooters.
  • Use AI routing to avoid congested areas.
  • Offer subsidized rides to encourage adoption.
• Expected Benefit: 25% faster deliveries, reduced carbon emissions.

C. NTC: Smart Traffic Management System

• Problem: Kathmandu traffic causes NPR 2 billion/year in losses.
• Proposal Idea:
  • Install AI-powered traffic lights (like Singapore’s SCATS system).
  • Integrate with Google Maps/Waze for real-time updates.
  • Pilot in Thapathali and Kalanki (high-congestion zones).
• Budget: NPR 500 million (funded by ADB or government).

7. Common Mistakes to Avoid

8. Step-by-Step: Writing Your Own Proposal

Let’s apply this to a real Nepali scenario: Problem: Your college’s Wi-Fi is slow during exams, causing students to lose time.

Step 1: Problem Statement

"During the last semester’s final exams, 40% of students reported Wi-Fi speeds below 2 Mbps (vs. the 10 Mbps required for online exams). This led to a 15-minute average delay per student, costing the college NPR 500,000 in lost productivity."

Step 2: Objectives

• Increase Wi-Fi speed to ≥8 Mbps in exam halls.
• Reduce login failures from 20% to <5%.
• Achieve this within 2 months.

Step 3: Methodology

1. Audit: Check current router capacity and interference sources.
2. Upgrade: Replace 10-year-old routers with Ubiquiti UniFi (NPR 200,000).
3. Optimize: Use VLANs to prioritize exam traffic.
4. Test: Run speed tests with 500 users during mock exams.

Step 4: Budget

Step 5: Risks & Mitigation

Step 6: Conclusion

"This proposal ensures a smooth exam experience for students. We request approval to proceed with the router upgrade by [date]. Let’s schedule a meeting to discuss further."

Exam Tip: How to Score Full Marks

1. Structure is Key:

   • Follow the proposal format strictly (title page → executive summary → problem statement → ...).
   • Use headings and bullet points for readability.

2. Use Real Data:

   • Exams often ask for examples. Cite Nepali contexts (e.g., eSewa, NTC, banks).
   • If no data is given, invent plausible numbers (e.g., "A survey of 100 TU students found...").

3. Problem-Solving Questions:

   • For "Write a proposal for a problem at your college," pick a specific, solvable issue (e.g., Wi-Fi, library management).
   • Show how your solution works (e.g., "We’ll use Trello for task tracking").

4. Avoid Common Pitfalls:

   • ❌ Generic statements ("The problem is bad" → ✅ "The problem is that 60% of students fail to submit assignments on time due to unclear deadlines.").
   • ❌ No timeline/budget → Always include a simple table or Gantt chart.

5. Practice Writing:

   • Draft 2-3 proposals (e.g., for a startup pitch, a college project, or a government grant).
   • Get feedback from peers or instructors.

Final Reminder:

"A proposal is a sales pitch for your idea. Make it clear, data-driven, and persuasive—just like a business plan!"