Institution Building

Drew Product Management Association

I designed Drew University’s first proposed product-management association as an interdisciplinary career-access institution, with a founding board, constitution, program model, and launch roadmap.

Role: Founder and President
Category: Institution Building
Timeframe: April 2025 — Present
Status: Pre-launch · Institutional approval pending

Pre-launch institution

Project Context

I began developing Drew PMA after recognizing that students interested in product work had no dedicated campus community, shared learning structure, or visible route from curiosity to practice. The project therefore became more than a club proposal: it required a mission, member value proposition, program model, governance system, founding team, launch plan, and a realistic understanding of the university dependencies that determine whether the institution can operate.

This case study documents the institution that has been designed and the work completed before launch. It does not present proposed meetings, speakers, trips, membership, or student outcomes as events that have already occurred.

Founding executive roles

President, Vice President, Secretary, and Treasurer form the proposed elected executive board.

Program formats

The initial portfolio spans education, practice, professional exposure, and career preparation.

Constitutional articles

The governance system covers mission, membership, officers, meetings, voting, and amendments.

Membership floor

The constitution sets sixteen fully matriculated students as the minimum operating membership, not a current membership claim.

Institutional problem

A career pathway students should not have to discover alone

Students can complete college without encountering product management early enough to explore the field, build relevant experience, or understand how their academic background could translate into product work. Drew currently lacks a dedicated community, learning structure, and visible pathway for closing that gap.

Opportunity definition

A field without a campus doorway.

The problem was not that product-management information did not exist. It was that students lacked a local, recurring, and socially supported way to discover the field, practice it, and understand how their own academic background could contribute.

Late discovery

Students may encounter product management only after internship recruiting has already begun, leaving little time to understand the field or build relevant evidence.

No dedicated campus pathway

Product work sits between business, technology, research, design, and communication, but Drew does not currently have one organization connecting those interests.

Fragmented preparation

Resources exist online, but students still need a local structure for practicing case analysis, asking questions, receiving feedback, and learning with peers.

Narrow career framing

Without an interdisciplinary entry point, students may assume product management is reserved for a specific major or technical background.

Mission architecture

Building leaders, not only applicants.

The mission connects career access with Drew’s emphasis on the whole person. Product management becomes a vehicle for practicing interdisciplinary problem solving, critical thinking, communication, ownership, and decision-making under uncertainty rather than an isolated technical or business track.

Community

Create an inclusive campus space where students across majors can meet collaborators, exchange perspectives, and grow together.

Education

Make product careers and concepts more legible through beginner-friendly sessions, practical resources, and direct access to professionals.

Experience

Move beyond classroom theory by giving members structured opportunities to analyze products, practice decisions, and lead initiatives.

Mindset

Develop curiosity, accountability, communication, and comfort with uncertainty rather than treating the organization as only a resume credential.

Positioning principle

Community first. Career value follows from shared practice, ownership, and access to people who make the field understandable.

Audience strategy

Designed for multiple entry points.

The organization is not designed only for students already pursuing PM internships. It must support discovery, career exploration, practice, and leadership without requiring prior experience.

Audience

Underlying need

Designed value

Curious beginners

Underlying need

A low-pressure explanation of what product management is and whether it connects to their interests.

Designed value

Beginner-friendly sessions, shared language, and exposure before specialization is required.

Career explorers

Underlying need

A clearer understanding of roles, recruiting pathways, and the evidence expected in product-oriented applications.

Designed value

Career conversations, mock interviews, speakers, and peer preparation.

Aspiring builders

Underlying need

Ways to practice problem framing, prioritization, research, product critique, and cross-functional communication.

Designed value

Teardowns, case studies, workshops, and student-led product initiatives.

Interdisciplinary contributors

Underlying need

A setting where perspectives from sociology, psychology, business, economics, design, languages, and other fields are treated as product strengths.

Designed value

Cross-major collaboration and visible ownership opportunities within a liberal-arts environment.

Institution design

Treating a student organization as a product system

I treated the organization itself as both a product and an institution: defining the unmet need, target audience, mission, value proposition, founding team, governance system, membership model, program portfolio, launch roadmap, and university dependencies required for the organization to operate responsibly.

Program portfolio

Turning curiosity into repeated practice.

The proposed activities form a portfolio rather than a list of disconnected events. Each format serves a different job across awareness, skill building, professional exposure, and career access.

Build product judgment

Product teardowns and case studies

Analyze how existing products frame user problems, make tradeoffs, position value, and connect design choices to business outcomes.

Reduce recruiting friction

Mock interviews

Practice product sense, execution, behavioral, and analytical interview formats in a peer-supported environment.

Make the field tangible

Guest speakers

Bring product managers, growth professionals, analysts, and adjacent practitioners into direct conversation with students.

Extend learning beyond campus

Convention and field experiences

Pursue opportunities such as ProductCon when institutional funding, scheduling, and approval make participation feasible.

Improve career access

Career conversations

Partner where possible with campus offices and student organizations to explain recruiting timelines, role differences, and preparation strategies.

Create a shared foundation

Product-management foundations

Introduce what PMs do, how multidisciplinary teams work, and how tools such as PRDs, research, analytics, and AI fit into the discipline.

Member journey

A pathway from discovery to ownership.

The organization’s intended value compounds over time. Students should be able to enter with curiosity, build understanding, practice with others, form useful relationships, and eventually own part of the institution themselves.

01
Discover
Encounter product management early enough to consider it as a field rather than learning about it at the end of college.
02
Understand
Develop a working vocabulary for users, product decisions, viability, prioritization, research, and cross-functional work.
03
Practice
Apply the concepts through teardowns, cases, mock interviews, and structured discussion rather than passive content consumption.
04
Connect
Build relationships with peers, alumni, campus partners, and practitioners who can make the career path more navigable.
05
Lead
Propose initiatives, own programming, serve on committees, and help shape an institution designed to continue beyond its founders.

Strategic translation

Converting the access problem into institution design.

I treated the association as a product whose users, experience, operating rules, dependencies, and continuity all needed to agree. The decisions below connect the observed access problem to a specific structural response.

Signal

Interpretation

Institution decision

Product management crosses disciplines

Interpretation

A business-only identity would exclude many of the perspectives that make product work effective.

Institution decision

Position Drew PMA as an all-majors practice community grounded in interdisciplinary collaboration.

Students need practice, not only information

Interpretation

A lecture series alone would explain the field without helping members develop evidence of product judgment.

Institution decision

Combine informational sessions with teardowns, mock interviews, cases, and student-led initiatives.

One-off events do not create a pathway

Interpretation

Career access becomes fragile when every experience depends on a single organizer or isolated speaker event.

Institution decision

Design a repeatable cadence, elected leadership structure, documented governance, and program portfolio.

Members should shape the institution

Interpretation

A founder-controlled club would conflict with the goal of creating ownership opportunities for students.

Institution decision

Give members voting rights, initiative pathways, committee opportunities, and formal influence over programming.

The university is part of the system

Interpretation

Approval, advising, funding, scheduling, and student-organization policy determine what can actually launch.

Institution decision

Treat institutional dependencies as product constraints rather than presenting the organization as operational before approval.

Operating model

Designing for repetition, not spectacle.

A successful first event would not be enough. The model needs to produce recurring value at a scale student leaders can operate, document, and eventually hand to a new executive board.

Recurring learning cadence

The proposed model uses regular meetings to build familiarity over time instead of concentrating all value in occasional flagship events.

Professional exposure

Guest speakers and career conversations connect abstract role descriptions to real career paths, tradeoffs, and organizational contexts.

Applied practice

Members work through product examples, frameworks, and interviews so participation produces stronger judgment and communication skills.

Cross-campus collaboration

Partnerships with academic departments, the Career Center, and other student organizations can expand reach without duplicating existing resources.

Member-led expansion

Students can recommend events, propose initiatives, and take responsibility for programs through committees or appointed roles.

Governance system

Making the institution larger than its founder.

The constitution turns broad values such as inclusion, accountability, and ownership into operating rules. Membership, officer authority, voting, meeting cadence, financial controls, removal, amendments, and succession are defined before launch so continuity does not depend on informal memory.

50%

Membership quorum

Voting actions require attendance from at least half of recognized members.

4×

Minimum meetings per semester

The constitution establishes a minimum recurring operating cadence.

25%

Special-meeting threshold

A quarter of the membership may request a special meeting in writing.

2/3

Removal and amendment vote

Major governance changes require a supermajority rather than unilateral founder control.

Open membership

Membership is open to Drew students and cannot be restricted on prohibited discriminatory grounds.

Earned participation

The constitution defines membership through attendance at two consecutive meetings, connecting rights to demonstrated participation.

One member, one vote

Members hold equal voting rights, with no absentee or proxy voting for organizational decisions.

Documented accountability

Officer duties, warnings, removal standards, meeting notice, voting records, and constitutional amendments are explicitly governed.

University integration

A faculty or staff advisor, university accounting rules, and Student Activities oversight are built into the operating model.

Succession by design

Annual elections, vacancy procedures, and role definitions create a path for the organization to continue beyond the founding team.

Leadership system

Separating ownership across clear roles.

The four-role executive board creates functional ownership while preserving member control through elections, voting, and removal procedures. Additional officers and committees may expand capacity when responsibilities are explicitly documented.

President

Coordinates meetings and programming, prepares budget requests with the Treasurer, and serves as the Student Activities liaison.

Vice President

Provides continuity when the President is unavailable, presides over executive meetings, and supports assigned operating work.

Secretary

Maintains minutes, votes, notices, communications, and an accurate membership record.

Treasurer

Maintains financial records, supports budget requests, and ensures funds remain within the university accounting system.

Launch dependencies

The institution exists on paper before it can exist in practice.

Student organizations operate inside a larger institutional product. Recognition, advising, funding, scheduling, accounting, membership, and policy are not administrative details outside the experience; they determine what members can actually access.

Institutional approval

The organization cannot represent itself as fully launched until the university completes its recognition and approval process.

Budget and resource access

Speakers, travel, conventions, materials, and larger events depend on available funding and university purchasing processes.

Advisor and administrative support

A qualified faculty or staff advisor is required and can help translate the program into an institutionally viable calendar.

Founding membership

A durable launch requires enough participating students to meet institutional and constitutional expectations without overstating early interest.

Repeatable programming

The first events must demonstrate a cadence the next executive board can realistically inherit and operate.

Planned measurement

Defining value before claiming impact.

These measures describe how the organization should be evaluated after approval and launch. They are not current performance results.

Awareness

Students reached across majors
Intro-session attendance
Interest and membership conversion
Ability to explain the PM role

Engagement

Repeat meeting attendance
Participation in discussion and practice
Member-proposed initiatives
Committee and leadership involvement

Learning

Completed teardowns and cases
Mock-interview participation
Self-reported confidence with PM concepts
Quality of product reasoning over time

Institutional durability

Successful event cadence
Cross-campus partnerships
Documented operating processes
Officer succession and continuity

Current state

Institution designed. Launch evidence still ahead.

Completed

Defined the organization’s mission and relationship to Drew University’s liberal-arts mission
Established an interdisciplinary positioning open to students across majors
Formed a four-role founding executive structure
Drafted a seven-article constitution covering membership, governance, meetings, voting, and succession
Designed an initial six-format program portfolio
Created an introductory presentation explaining the field, member value, and proposed roadmap
Defined member ownership through voting, initiative proposals, committees, and elected leadership
Documented the institutional approvals, funding, advising, and membership dependencies required for launch

Pending

Receive final university recognition and budget decisions
Confirm the faculty or staff advising structure
Establish the recognized founding membership
Finalize the first-semester calendar and meeting cadence
Schedule the first guest speaker and collaborative events
Validate which program formats create repeat participation and learning value
Develop officer handoff materials and a repeatable operating playbook
Collect real attendance, engagement, learning, and career-access evidence after launch

Evidence boundaries

A proposal is not a launched community.

The case study can demonstrate institutional thinking, governance, program design, and launch preparation now while reserving claims about members and outcomes for the point when real participation can be measured.

What I can claim

The mission, value proposition, governance structure, executive roles, and proposed programming are documented
The organization is intentionally designed as an interdisciplinary, beginner-friendly pathway into product management
A founding executive structure and introductory materials have been prepared
The constitution creates formal member rights, officer accountability, voting procedures, and succession mechanisms
The project remains pre-launch while institutional dependencies are unresolved

What I am not claiming yet

That Drew PMA is already an officially operating student organization
That the proposed sixteen-member floor has been reached
That any speaker event, convention trip, collaboration, or workshop has already occurred
That members have achieved recruiting, learning, or career outcomes
That the proposed programming mix has been validated through attendance or retention data
That university funding or external partnerships have been secured

Reflection

Access needs an institution, not only an invitation.

The real product is a durable path through which students can discover a field, practice it together, and eventually take ownership of the community that helped them enter it.

Designing Drew PMA has reinforced that institution building is product work. The mission must connect to a real need, programming must serve different member jobs, governance must distribute authority, operations must survive leadership turnover, and launch claims must remain honest about dependencies. Approval delays limit what can be demonstrated today, but they also reveal the systems that determine whether access becomes reliable or remains only an idea.

Credits