Case Study
A Cloud Platform for a Nation's Defence Force
In partnership with the Australian Defence Cooperation Programme in Timor-Leste, Similie was tasked with developing a cloud-based Personnel Management System for F-FDTL, the Timor-Leste Defence Force. Their existing PMS was a Microsoft Access database stored on a single computer at the Dili HQ. As the sole Product Designer on the project, I owned the design end-to-end, but this was as much a change management project as a design one: an entire organisation was moving from a single-computer database to a cloud platform, and my involvement at every stage, from the first stakeholder workshops through to the training sessions where real records went into the system, was a large part of why the transition succeeded.
- My role
- Product Designer (sole designer on the project)
- Team
- Similie product and engineering team, including a product manager and a remote development team
- Duration
- 2018–2021
- Status
- Shipped and in use

Context & Challenge
F-FDTL's personnel records lived in a Microsoft Access database on one central computer. Updating or maintaining it meant physically being at the Dili HQ; a cloud-based solution would let authorised staff log in and manage the database from anywhere.
The project ran alongside the development of F-FDTL's Logistics Management Platform, and both were built into One, Similie's ERP platform, so the new system had to extend an existing product rather than start from a blank page. An initial series of MoSCoW workshops with key stakeholders established the needs and requirements for both systems. The stakeholder landscape was genuinely complex: a national defence force, an international defence cooperation programme, and a distributed product team, working across languages and cultures. And beyond the interface itself, the project asked an organisation to change how it worked, which meant the design process had to bring people along, not just produce screens.

Approach
Start from the data, not the screens.
The existing PMS gave us a picture of the information the new system needed to store, and we cross-referenced it against the personnel records of the Australian military, which surfaced additional categories. Through card sorting workshops with F-FDTL personnel, we organised all of this into categories and built the initial taxonomy for the data.
Let wireframes surface the hard questions.
Wireframing forced us to go much deeper into the datasets than the workshops had. Questions like: which religions to include, and in what order? What are the categories for disciplinary actions? Which languages belong at the top of a dropdown? Answering these with stakeholders early meant the built product reflected the organisation's reality rather than our assumptions.
Design the platform to outlive the project.
The client wanted a platform that could evolve with the organisation, so rather than hard-coding every field, I designed an inline editor (think Notion, Webflow or WordPress) that lets a system administrator add and modify parameters directly in the UI. It took time to design upfront, but it removed the need for engineers to update parameters later, and meant we didn't have to design every single page of the platform.
Test with the people who would actually use it.
We invited a focus group to the Similie office to test the first build, capturing issues across translations, descriptions, performance and design. A smaller stakeholder group then reviewed the issues raised, and we used Notion to turn them into an actionable task list for the team.
Support the rollout, not just the release.
Once the platform was ready for first release, we ran a series of data collection and training sessions with the primary user group. These sessions were where the change management became real: the same people who had shaped the taxonomy in the early workshops were now being trained on the finished system, and the sessions doubled as research, identifying further improvements as real records went in.


Collaboration
I worked with all of the key stakeholders throughout, from the MoSCoW workshops through card sorting, usability sessions and training. During development I worked closely with the product manager, sharing responsibility for regular meetings with our remote team, performing QA, and providing feedback on the build. Staying present across the whole arc, rather than handing off after the design phase, kept trust high on the client side and quality high on the build side.

Outcomes & Impact
- Successful delivery of a SaaS platform, now shipped and in use, that enables the Timor-Leste Defence Force to manage their personnel with greater ease, replacing a single-computer Access database with a system accessible from anywhere.
- The organisation actually made the transition. Continuous involvement from workshops through to training meant the people using the system had helped shape it, which made adoption a continuation of the process rather than a hurdle at the end.
- The inline parameter editor made the platform self-serve for administrators, reducing the need for engineering involvement in routine changes and letting the system evolve with the organisation.
- Usability testing, iteration rounds and training sessions caught translation, content and performance issues before and immediately after first release.
Reflection
This was designing for an organisation as much as for individual users, and the design work and the change management were never really separate. The biggest lever wasn't a screen; it was the combination of making the platform's structure editable by the client and staying involved from the first workshop to the last training session, which changed the project from "deliver a system" to "hand over a capability."
Key Learnings
- Change management is a design responsibility. Being in the room from workshops to training, not just for the design phase, is what turned a delivered platform into an adopted one.
- Building the taxonomy with stakeholders, through card sorting and workshops, surfaces organisational realities (categories, hierarchies, sensitivities) that no amount of desk research would.
- Making a system self-serve is a design decision with compounding returns: slower upfront, faster forever after.
- In cross-cultural, multilingual work, testing in context is non-negotiable. Translations, terminology and training are part of the product, not an afterthought.
Testimonials
“I would put James on any problem that requires detailed thinking and systemic, organized design. Plus, he's just a likeable chill guy.”

Garrett Schultz
Creative Director & Art Curator
“James Newton lead the change in the way we designed products at Blockade Games.”

Kyle Chivers
Operations Officer at Blockade Games
“James excels at simplifying... complexities for users, with designs that both explain to and inspire the user.”

Benjamin Heidorn
CTO, Co-Founder at Blockade Games
“James is a practiced designer with a unique combination of skills and life experiences — a strong creative energy paired with a keen sense for aesthetic harmony. I would recommend James without hesitation.”

Adam Smith
CTO & Co-Founder at Similie
Let's chat, drop me an email or connect on LinkedIn
© 2026 James Newton. Product Design
92a6438 · 1 aug 2026 · colophon · design system