Community Technology ProjectsUW-Stevens Point · CNMT 479 & 480

UWSP technology students · CNMT 479 & 480

Your next project.
Their next step.

Have a technology project that could make a difference for your organization? Work with UWSP students as they apply technology, data, and problem-solving skills to a real need.

A few sentences are enough to start. No finished proposal needed.

Student work. Community impact.

Featured success story
2

Helping people find a connection to their past.

Two students provided a tremendous service to Saxeville Union Cemetery: a website that lets visitors find ancestors, locate grave sites, and explore cemetery information from a web browser.

Visit the Saxeville Union Cemetery website

From an idea to a project

Start with a conversation.

You know your organization. Students bring their skills and a willingness to learn. Together, we find a workable scope.

01 / SHARE THE NEED

Tell Andy what you have in mind.

Describe the problem, what a useful result would look like, and any timing or technical constraints. An email or a brief conversation is enough.

02 / PLAN IN CNMT 479

Shape a project students can take on.

Students explore candidate projects, select one, work with the organization to define scope and deliverables, and develop a plan for approval.

03 / CARRY IT OUT IN CNMT 480

Work together as the project develops.

Students carry out the approved project with faculty guidance, regular client communication, and reviews of their progress and deliverables.

Timing matters. Projects follow the academic calendar, with planning before the capstone semester. Share your preferred timing so Andy can discuss the next suitable opening. Smaller pieces of work may occasionally fit a current student's needs.

What could students work on?

A useful problem is a good beginning.

Projects can vary in size and technology. Here are a few possibilities to discuss.

  • App development, websites, and web applications
  • User experience and interface design (UX/UI)
  • Data analysis and practical applications, including reporting tools and databases
  • Cybersecurity and digital security
  • Networking
  • System integrations, including connecting cloud-based software (SaaS)
  • Workflow improvements, automation, or a manageable piece of a larger project

Have something else in mind? Contact me about other project types. You don't need to know which category your idea fits. Start with a problem you'd like to solve or something you'd like to improve, and we can explore the possibilities together.

A partnership with a purpose

Value on both sides.

For your organization

An opportunity to move useful work forward, gain fresh perspectives, and connect with emerging technology professionals.

For students

Experience working with real people, needs, and constraints. Practice communicating, solving problems, and adapting as a project changes.

Your part: help define the need, provide an available contact, and offer feedback as the work develops. We'll discuss access, resources, and expectations when we explore the project.

Let's explore the possibilities

What would be useful to you?

Share what you know. The details can develop through conversation.

Andy ThompsonInstructor · UWSP CNMT 479 & 480anthomps@uwsp.edu715-252-4277

Prefer to talk? Email or call to arrange a conversation in person, by phone, or by video.

What happens next?
Andy reviews the idea and discusses whether it fits the students, course timing, and available capacity. Submitting an idea begins that discussion; it does not guarantee selection.

Share a project idea

Required fields are marked with an asterisk.

Please keep confidential information out of this first message. A general description is enough.

Your idea and contact details will be saved for Andy to review.

A few things you might be wondering.

Does the idea need to be fully defined?

No. Start with the need and the result you hope for. Students refine the scope and deliverables during pre-capstone, with feedback from you and the instructor.

Can I suggest more than one project?

Yes. Share a range of possibilities, including smaller parts of larger projects. A project does not need to cover every topic taught in the course.

What about costs, access, or ongoing support?

Bring those questions to the first conversation. Any expenses, access needs, ownership of deliverables, and expectations for support after the semester should be discussed before a project is agreed upon.

Who should get involved?

Business owners, IT and operations leaders, nonprofit directors, and other organizational contacts with a technology need are welcome to start a conversation. An available contact who can answer questions and provide feedback helps make the project workable.