Green Shoe Garage / Product development boot camp

Build it.Test it.Make it again.

Three hands-on days connecting design, mechanical development, electronics, software, and testing—with a practical plan for your first small production run.

Ask about the boot camp Explore the three days ↓

Live online or in person · Small groups · Real hardware

Read the instructor manual (PDF, opens in a new tab) ↗

On the bench / Workshop monitorConcept illustration

Enclosure + circuit + code + evidence.
A common project carries the learning from the first sketch to a first-batch plan.

Duration: 3 days
Instruction: 18 hours
Planned cohort: 6–8 people
Delivery: Online / in person

The whole product, on one bench

The enclosure affects the sensor. The code affects the test. It all connects.

A product is a collection of decisions that have to work together. In this boot camp, you’ll follow one physical product through the development cycle: define its job, make design choices, integrate its parts, investigate failures, and prepare the information another person would need to build it.

Design
Mechanical
Electronics
Software
Testing
Production preparation

Expect short explanations, practical demonstrations, guided work, and design reviews. You’ll finish with a learning prototype, a documented set of decisions, and a draft low-volume production plan. A commercial release needs further engineering and qualification.

The three days

From “what if?” to “here’s how.”

Six connected modules. One shared project. Each session adds something you can inspect, test, or hand to the next person in the development process.

Day01

Define it.
Give it form.

Leave with: a product brief, measurable requirements, and a reviewed enclosure change.

Morning / Design

Make the problem specific.

Identify the user, use case, constraints, and success criteria.
Compare concepts and sketch the product architecture.
Write requirements you can actually verify.
Connect user needs to engineering decisions.

Afternoon / Mechanical

Design around the real parts.

Modify an enclosure using supplied CAD source.
Check fit, clearances, tolerances, and mounting.
Consider materials, fabrication, assembly, and repair.
Review cable access, controls, and sensor placement.

Day02

Wire it.
Make it respond.

Leave with: an inspected circuit, a firmware change, and an integration record.

Morning / Electronics

Turn interfaces into connections.

Read the connection map and identify components.
Assemble a USB-powered, solderless circuit.
Connect a sensor, indicators, and a button.
Inspect before power-up and investigate wiring faults.

Afternoon / Software

Make behavior explicit.

Upload and modify the reference firmware.
Read sensor data and interpret serial logs.
Explore normal, alert, and fault states.
Handle button input and integrate code with hardware.

Day03

Prove it.
Plan the next 25.

Leave with: test evidence, a first-batch estimate, and a draft production handoff.

Morning / Testing

Replace assumptions with evidence.

Link tests to requirements and acceptance limits.
Exercise normal behavior and fault conditions.
Investigate a failure, make a change, and retest.
Record results, configuration, and open issues.

Afternoon / Low-volume production

Prepare for a repeatable build.

Develop a bill of materials and sourcing questions.
Estimate parts, labor, yield, and setup costs for 25 units.
Draft assembly instructions and acceptance tests.
Review file revisions, release blockers, and next steps.

Typical day: 9:00 am–4:30 pm, including two 15-minute breaks and a one-hour lunch. Each day contains six instructional hours. Dates and the course timezone are confirmed for each cohort.

The reference build

A small monitor.
A complete development story.

Build a USB-powered workshop environmental monitor that reads temperature and humidity, signals its operating state, and records data. Its scale keeps the build manageable while exposing the decisions that matter in a much larger product.

Why does an enclosed sensor read differently? Can someone assemble the unit from your notes? What does the software do when data is missing? Those questions become the work.

Mechanical: An editable enclosure with mounting, ventilation, and access decisions.
Electronics: A microcontroller, temperature/humidity sensor, LEDs, and a pushbutton.
Software: Sensor readings, explicit operating states, input handling, and diagnostic logs.
Evidence: Requirements, test records, revisions, and a draft 25-unit build plan.

The reference device is a classroom prototype, not a safety alarm or calibrated measurement instrument. The illustration above shows the concept; the prepared kit determines the physical build.

Who belongs at this bench?

People ready to turn an idea into something tangible.

A good fit for

Founders and inventors evaluating a physical product idea.
Makers ready to develop beyond a one-off prototype.
Designers, engineers, and developers who want to understand the neighboring disciplines.
Small teams that need a shared approach to development and manufacturing handoffs.

What to bring

Curiosity, a laptop, and comfort working with files and installing software. Introductory CAD and coding support is built into the guided exercises.

You can bring a product idea to think through alongside the common project. Everyone uses the prepared reference build for the core practical work, so the three days stay focused and achievable.

Tell us about access needs or computer restrictions when you inquire so we can plan appropriate support.

Two ways to join

At our bench.
Or at yours.

Both formats follow the same 18-hour curriculum and practical checkpoints. Small cohorts leave room for questions, troubleshooting, and individual review.

01 / In person

Build together in the room.

Work alongside the instructor with close-up demonstrations, shared reviews, and supervised hardware support.

Three full workshop days.
Prepared components and enclosure parts for the labs.
Face-to-face design reviews and troubleshooting.
Your own laptop, with a setup check before class.

Venue, dates, kit arrangements, and the final equipment list are confirmed for the cohort. Ask about a private session for your team.

02 / Live online

A guided workshop at your desk.

Follow live bench-camera demonstrations, share your screen, and build the same reference project with instructor checkpoints.

Three full teaching days; spacing them a week apart is recommended.
A prepared hardware kit arranged before the course.
A solderless build and pre-course USB/software check.
A laptop, reliable internet, and a camera or phone for close-up views.

Kit delivery, shipping availability, tools, and the published timezone are confirmed before enrollment. A 3D printer is not required.

Training a team? Ask about a private cohort. A company-specific reference project can be scoped in advance, with the exercises adapted to the work your team needs to do.

Discuss team training →

A closer look at the course

Read the instructor manual.

Explore the full three-day teaching plan, from the first product brief through testing and preparation for a small production run. The manual includes timed lessons, guided labs, worked examples, assessment criteria, and 12 reusable BenchBook worksheets.

Read the manual ↗Download PDF ↓

43 pages · PDF · Instructor edition 1.0 · October 2026

Before you join

A few practical questions.

Have something else in mind? Talk to us.

Do I need to be an engineer or know how to code?

No engineering qualification is required. You should be comfortable using a computer and installing software. We supply a starting design and firmware, then guide you through specific changes. This is an introduction to the full development process; it does not replace specialist training in each discipline.

Will I work on my own product idea?

You can apply the decisions and worksheets to your own idea, but assessed practical work uses the common workshop-monitor project. That keeps hardware, support, and timing manageable. Private team courses can use an adapted project agreed in advance. Share only the details you are comfortable discussing in a group.

Do I need a 3D printer or soldering equipment?

No. Required enclosure parts are prepared ahead of the course, and the reference circuit is solderless. The preparation sheet lists the laptop, basic tools, multimeter, and kit arrangements for your cohort. Online participants complete a software and USB connection check before class.

Will my product be ready to manufacture after three days?

You will have practiced the process and drafted a production handoff for the course project, including a 25-unit planning exercise. Commercial production still requires product-specific engineering, qualification, supplier confirmation, and any applicable compliance work. Identifying those remaining steps is part of the course.

What does low-volume production preparation cover?

Parts and sourcing, assembly time, yield assumptions, setup costs, design for assembly and test, file revisions, inspection records, and acceptance criteria. You will consider what a second builder needs and which open issues should hold up a batch.

Will I receive a certificate?

A certificate of completion is available when the course’s participation and practical evidence requirements are met. It records completion of the boot camp; it is not a professional license or an accredited engineering qualification.

What are the dates and price?

Public dates and tuition have not been announced. Contact Green Shoe Garage for the next cohort or a private team session. We’ll confirm the delivery format, schedule, venue or timezone, kit and shipping arrangements, and full price before you enroll.

Let’s put something on the bench

Bring your curiosity.
Leave with a plan.

Dates & pricing by inquiry.
Online, in person, or a private team session.

Tell us a little about yourself and the kind of product you want to understand. We’ll help you work out whether this boot camp is a fit.

Your preferred format and location or timezone.
Whether you’re joining individually or with a team.
Your experience, interests, and preferred dates.

Ask about dates & pricing →

Mention “Product Development Boot Camp” in your message.
Or email [email protected]
+1 301 880 4538