About
A practice built around adoption evidence
DevCloud Suite exists because licences on a spreadsheet rarely match what internal business applications do on a Tuesday afternoon. We stay close to that gap.
Origin
The practice started in Gwangmyeong-si after repeated renewal cycles where finance asked why suite seats were quiet while project teams insisted training had been “completed.” Someone needed to sit with application owners, watch artefact handoffs, and write findings that survived a leadership meeting.
We kept the work deliberately narrow: cloud suite adoption analytics for internal business applications. We do not rebuild systems, renegotiate vendor contracts, or run open-ended transformation programmes.
How we approach clients
Interviews stay on tasks and exceptions. Heatmaps stay small enough to discuss. Recommendations name people and calendar moments. When evidence is thin, we say so instead of colouring cells to look complete.
Values in the room
- Respect for operator time — no feature demos disguised as research
- Plain language in briefings, including the word “wait” when needed
- Separation between analysis and vendor sales pressure
- Follow-through only when a prior baseline exists
Based in Gyeonggi-do
Fieldwork covers the Seoul–Gyeonggi corridor on site when observation requires it; interviews and briefings run remotely when that serves owners better.