The plan exists.
But there is no picture of it.
In a large-scale redevelopment, the master plan is already in place. It states the goal of "realizing a smart city." But what that actually means in practice is not shared among the stakeholders.
This pattern recurs across the assignments we take on. Technology catalogs are everywhere, but the language connecting them to a specific site and business plan is missing. Do you install sensors, or build an app? Who is it for, and what does it measure? Without criteria for judging these questions, the list of candidate technologies just keeps growing.
Before researching,
decide what to research.
We don't start with case studies. We begin by holding repeated discussions with the developer to put the district's intended future into words.
Together we work through the master plan, mapping out current technologies and the social issues likely to surface down the line. From there we work backward from the completed state to sketch an ideal picture. Only after this step can we decide which districts to study, and what to look for.
They are material for judgment.
On one engagement, we ran four rounds of discussion alongside roughly 30 hours of research. We brought findings back to the table, debated them, and let the outcome of each debate decide what to look into next. That back-and-forth is what separates a mere collection of case studies from material you can actually use.
We don't line up
only the success stories.
We chose districts of very different character and organized their governance structure, scale, intended vision, and implemented services within a single framework — including cases that didn't go as planned, not only the ones that succeeded.
- TYPE 01Corporate-led, healthcare-focused innovation district (Nordics)A district developed adjacent to an R&D campus. We confirmed a structure in which resident services — a mobility-support app, mobility hubs, community events — are sustained through the developer's own investment.
- TYPE 02Campus city operated by a private developer (Baltics)One group handles development, real estate, education, healthcare and energy under a single structure. Notably, it provides pilot testing sites and support as a package, and continuously measures the district's performance against its own custom metrics.
- TYPE 03Government-led digital district (Southeast Asia)A shared platform integrating district-management systems underpins services such as delivery robots, payments, parking and lighting. We confirmed how much faster deployment becomes once the platform is built first.
- TYPE 04Privately led smart town (Japan)Conceived from everyday life rather than from technology, with a mechanism in which the operating company collects residents' feedback and partner companies turn it into services. We also tracked the revised concept ten years in, as the town entered its "second chapter."
- TYPE 05Public–private smart city (Japan)An initiative launched through a three-way partnership between government, business and a university. We mapped a design that simultaneously improves the convenience of civic services and creates jobs by attracting companies.
- TYPE 06International city conceived as a large-scale development (East Asia)A large-scale project that drew attention in its early days. While its use of data was advanced, resident-driven community-building was comparatively limited, and we also documented how misalignment among partner organizations diluted the original vision over time.
What documents don't show,
we go and ask.
Desk research alone can't reveal how a governance structure actually functions, or how residents really feel about it. We traveled to a smart-city exhibition held overseas and interviewed local government officials directly.
How are they addressing delivery-staff shortages? How are they helping older residents adapt digitally? How is privacy protection designed? How do they encourage civic participation? We prepared questions in advance and brought back the answers as a question-and-answer record.
The lesson we heard repeated most often was simply this: technology is a means, not an end. Don't get distracted by buzzwords — return to concrete problems like traffic congestion or access to healthcare. Start with a small pilot, then scale it horizontally. It was this basic discipline that separated successful implementations from the rest.
Don't aim for
the finished form from day one.
What the research pointed to was a structure for growing the data platform in stages: build the information infrastructure and convenience services first, add support functions in the middle that bring in the developer and residents, and only then layer on advanced services.
The middle layer is the one most often overlooked — liaison organizations, incubation facilities, community groups. Because these aren't technology elements, they tend to drop out of plans, yet they proved essential for bringing in more participating businesses, winning residents' understanding, and expanding the rollout area. It's no coincidence that so many of these districts have an area-management organization in place.
- EARLYNetwork infrastructure & data collection ／ Monitoring of environment, traffic and energy ／ Convenience services (traffic information, smart parking, facility booking, community apps, etc.)
- MID-STAGEBuilding partnerships beyond the district ／ Supporting business activity and providing a testbed ／ Building resident trust and communicating how to use the services
- LATEREnergy management ／ Optimizing urban planning with digital twins ／ Personalized services ／ Attracting outside operators for pilots
Data sovereignty stays with the landowning company, with external services connected via API as needed. Collection and use are handled jointly with a partner experienced in ICT infrastructure, data analysis and security. We also worked out the basic operating policy alongside this.
Building the platform
is not, by itself, an advantage.
In this kind of review, the idea of "building our own city OS and rolling it out to other regions" inevitably comes up. We give our honest view on it.
Building an integration platform from zero with technical capability as its core, then rolling it out as a framework to other regions or countries, is extremely difficult. There are already many precedents overseas, and starting the same thing today makes it hard to differentiate on technology alone.
It's the data only that place can produce.
On the other hand, if a district generates unique metrics and data that only it can produce, the know-how gained from that can contribute to solving problems elsewhere. The same applies to cases where resident behavior actually changed.
That's why the order of consideration matters: which content to start from, what data to capture from it, and how to accumulate and use it. If, for example, an area's core value is set as "ease of opening a storefront," the data worth collecting follows naturally. Content design → data strategy → clarifying the core and the moat — keeping this cycle in mind from the earliest stage makes a substantial difference to the value of smart services over the medium-to-long term.
On implementation, we also explain that a visualization-level build using a mapping library can be relatively inexpensive, while a full outsourced package carries a commensurate cost. Because we develop and operate Placebook ourselves, we can offer this judgment with first-hand experience behind it.
We've received
multiple requests with this same structure.
We have taken on multiple research and consulting engagements related to smart cities and urban DX. Our clients have ranged from developers to municipal governments to university institutions.
We have handled multiple smart-city research engagements focused on the Nordic countries in particular. The initiatives under way in cities across Denmark, Sweden and Finland are worth referencing not only for their level of technical implementation but for how they design civic consensus-building and behavior change — and we have built ongoing relationships with institutions on the ground there. The network we built through our International City-to-City Collaboration work underpins the depth of this research.
We also conduct research on area-management organizations, both in Japan and abroad — who operates a district, funded by what, and how it mediates between government, landowners, tenants and residents. This research lines up organizational form, revenue structure and functions side by side. The question of "who should operate it," often overlooked in smart-city planning, is informed by this body of knowledge.
What these engagements have in common is that we're brought in not for the technology deployment itself, but for the stage of deciding "what are we aiming for, and what should we measure to get there." Because we hold urban planning, spatial design, data analysis and product development in-house, we can handle everything from concept through feasibility review as one continuous process.
