✅ Why this step helps you avoid dead ends (and find smart shortcuts)
You know who you’re building for and what they need—now figure out how it might work.
Technology research explores the tools, platforms, materials, and techniques that could bring your idea to life. It helps you understand what’s already available, what’s emerging, and what’s feasible within your time, cost, and capability limits. It reduces risk, accelerates design, and prevents wasted effort chasing the wrong tech.
📘 What you’ll investigate
- Relevant hardware platforms, modules, or development kits
- Off-the-shelf solutions vs. custom development trade-offs
- Available sensors, chips, APIs, or cloud tools
- Licensing, compliance, or supply constraints
- Costs, lead times, and compatibility with your team or supply chain
🛠️ Tools and methods
✅ Tech Research Checklist
Example Tech Research Table
| Function | Options Considered | Pros | Risks |
| Connectivity | LoRa, Wi-Fi, NB-IoT | LoRa = low power | NB-IoT coverage varies |
| Display | E-ink, OLED, LCD | E-ink = great in sun | Slow refresh rate |
| Control chip | ESP32, STM32, Raspberry Pi Pico | ESP32 = fast to dev | Pico lacks deep sleep |
- Document findings in a central place—Notion, Airtable, or a shared doc
- Revisit later as tech evolves—some “no” options may become viable later
⚠️ What to watch out for
- Falling in love with a technology before validating the need
- Choosing complex tech when simpler solutions exist
- Not checking licensing, availability, or support status
- Assuming “free” tools come without trade-offs
💡 From technical founders
“We spent three weeks trying to build a custom sensor—then found an off-the-shelf version for £2. Tech research doesn’t slow you down. It saves you.”– CTO, AgriTech Pilot Startup
💡 Research the boring stuff too—like battery life, casing materials, or connector types. They’ll trip you up later if ignored now.
🔗 Helpful links & resources
- Tech Research Mapping Template
- Download: Feature–Tech Fit Grid
- Article: How to Explore Technologies Without Getting Stuck in the Weeds
- Follow-on: Viability Sprint
✍️ Quick self-check
🎨 Visual concept (optional)
Illustration: A comparison board shows three tech options for “connectivity”. Each option has icons for cost, power, dev speed, and compatibility. A team member tags one “Risky but powerful”, another “Easy to prototype”.
Visual shows how structured tech research builds confidence and avoids unnecessary complexity before you commit.
