Philosophy and approach
Development approach
We're at our best building MVPs — minimum viable units — and improving them while watching how they get used.
While staying mindful of cost and time-to-effect, we share the reasoning behind decisions and design intent so you can move forward without worry.
If what you want doesn't exist yet.
Some things the world needs simply don't exist in the right shape.
HoshimonoDesign started by building, ourselves, the things we couldn't find — the "hoshimono" (things we wanted).
When existing products or services don't fit, instead of forcing the fit, redesign the shape so it fits the site.
That's where HoshimonoDesign began.
Build small, sharpen on-site.
We don't aim for a finished form from the start.
We launch with the minimum features, validate them in real operation, and improve precision iteration by iteration.
This approach keeps deployment cost down, makes course corrections easy, and improves on-site adoption.
We believe "not over-building" leads to systems that stay useful for a long time.
We don't take everything on. IoT or hardware integration, large-scale development, and systems that assume 24/7 operation don't match this philosophy or our setup, so they're out of scope.
If what you want doesn't exist, build small, use it, fix it. We only work in domains where that cycle is sustainable.
Design with continued use as the premise.
HoshimonoDesign prioritises operability over flair.
- Fits the actual workflow — or changes the workflow to something realistic.
- Doesn't get complicated with extra features.
- Assumes handover and maintenance from day one.
- Handles data with a clear policy.
Technology is a means; the goal is "making site work easier and renewing the business."
Constraints and pacing
While working as a full-time employee, this is run as a side business, so short-term high-volume development and labour-intensive efforts aren't possible.
- We prioritise the pace of building small and sharpening in real operation.
- We value designs that complete on hand and keep them workable in high-reliability domains.
- Rather than mass-producing on impossible schedules, we choose designs that last.
What we can't do
- Short-term high-volume delivery
- Data entry or production that assumes labour-intensive effort
- One-off development without operational or business design
- IoT deployments or smartphone app development
Reach out
Even just sorting the issue is fine. We listen to the current state and design the smallest solution together.