The Ministry of Education and Research (opens in a new tab) (HTM) is an Estonian government agency responsible for ensuring the purposeful and effective development of education, research, youth, and language policies, as well as the high standard and competitiveness of national research and development. HTM also coordinates the development and administration of information systems across its sector.
The Ministry uses the Atlassian platform to support IT services, internal operations, reporting, collaboration, and area-of-government services. The true value of the platform emerges when the capabilities of Jira, Confluence, Assets, Forms, and add-on plugins are connected directly to concrete work processes.
To develop the system further, HTM brought in Trinidad Wiseman. TWN’s role went well beyond technical configuration. At the heart of the collaboration was understanding the business challenge, deconstructing each process, selecting the right Atlassian solutions, designing workflows, improving user experience, and swiftly delivering complex developments.
According to Toomas Adson, Atlassian Product Owner at HTM, it was clear by 2022 that the ministry needed more specialised support for its Atlassian solutions than internal teams could deliver at the required pace. Bringing in external expertise helped maintain development momentum and provided deep Atlassian knowledge for the most demanding tasks.
Complex workflows require more than technical configuration
The Atlassian platform offers extensive capabilities. That is a strength, but also a challenge, because having many options requires making the right choices.
HTM and its subordinate agencies needed to manage a wide variety of workflows:
- Request and enquiry management;
- Service ordering;
- Grant and subsidy reporting;
- Contract reviews;
- Committee and commission workflows;
- Collaboration platforms for external experts;
- Intranets and public web portals;
- Priority initiative reporting;
- Process creation and approvals.
None of these can be solved with a single technical template. For every process, it is essential to understand who the user is, what information they need, where the current bottleneck lies, and which workflow resolves the problem in the simplest way.
TWN’s core value lay in thoroughly analysing and deconstructing the business challenge before jumping into technical solutions. The ministry could define its need, and TWN provided practical options for solving it within the Atlassian ecosystem.
Three reasons why HTM brought in an Atlassian partner
Our approach: process first, solution second
TWN's approach did not start with asking which Atlassian feature to use. First, the workflow had to be clearly mapped out and understood.
A typical engagement consisted of four stages.
Three examples where TWN delivered tangible value
1. Service portals: from vague requests to a clear order journey
Harno’s Tugitee project clearly demonstrated why Atlassian developments need to start with understanding the underlying workflow.
The core problem was not simply technical. An internal habit existed where colleagues needed "something". Once they sent an email, a time-consuming back-and-forth began just to clarify the actual request. Requesters often did not know what additional details to provide, while the service team lacked a unified overview of incoming demand and where their team's hours were being spent.
Workshops facilitated by TWN examined these processes in detail. Through this work, services were clearly defined, inputs were mapped out, and agreements were reached on how forms should guide users to the right request.
The result was a clearer, more effective service portal:
- more than 20 services were formally defined;
- structured forms replaced ad-hoc email threads;
- requesters no longer needed to remember internal procedures by heart;
- forms proactively guide users to provide the correct inputs;
- service providers gained reliable performance statistics;
- ticket handling became fully transparent.
The same principle applies to other inquiry and service management workflows. TWN’s role is to help understand what is truly being requested, what data the team needs to get the job done, and how Atlassian can turn that logic into an effortless experience for the user.
2. Reporting and management information: insights generated on the go
For HTM, a primary reason for expanding their Atlassian footprint was work tracking. The goal was to reduce manual status reporting and automatically gain visibility into workload, project progress, and current outcomes directly from daily workflows.
This value emerged across multiple initiatives. Moving action plan monitoring into Jira significantly improved reporting quality and speed, bringing welcome transparency to ongoing work. The supervision department previously relied on document management systems, email, and Excel spreadsheets. While spreadsheets helped collect raw data, they failed to deliver adequate analytics. Similarly, municipal grant reporting required collecting data on tight deadlines and presenting it in the Haridussilm portal. For state budget grant applications, the aim was to shift work away from email into Jira to make both workflow status and statistics visible.
All these cases shared the same challenge: work was getting done, but management information had to be assembled manually after the fact, or was missing altogether.
TWN helped build these processes so that reporting data is captured as a natural part of daily work:
- users submit details through a guided form;
- Jira tracks the workflow and status;
- Assets links the task to the relevant entities or institutions;
- Power BI and Haridussilm deliver leadership dashboards directly from Jira inputs;
- nobody needs to draft separate manual progress reports.
Here, TWN’s core contribution was bridging process and data. The solution was not merely a form built in Jira, but a coherent workflow designed to generate the exact dataset needed for decision-making.
3. Knowledge management and collaboration: Confluence as an active workspace, not a file dump
At HTM, Confluence serves as an active environment for knowledge management and team collaboration. This sets it apart from a file-centric approach where information gets trapped in static documents, folders, or personal cloud drives.
TWN supported this transition across three main areas.
First, TWN helped turn Confluence into a practical collaborative workspace. For joint projects with external working groups, project spaces were set up where external experts can review documents, share information, and contribute directly. Compared with traditional SharePoint file structures, knowledge created in Confluence flows far more easily into everyday processes and across teams.
Second, TWN helped configure Confluence for designing and evolving HTM’s internal operational processes. Standard Word documents were ill-suited for co-creating workflows or managing version control. Using Confluence and Comala, they established an approval workflow that keeps track of modifications, formal reviews, and version histories for HTM process definitions.
Third, TWN helped leverage Confluence and Refined to launch public-facing web views quickly. When working groups needed to publish materials externally, building a separate website would have been slow and costly. Combining Confluence and Refined provided an intuitive, polished public view. The curriculum update project is an excellent example of how an internal workspace and a public portal can be created seamlessly within the same ecosystem.
What value does TWN bring to the collaboration?
According to Toomas Adson, TWN's greatest value lies in the ministry being able to present a business challenge, while TWN outlines different technical possibilities. At the same time, TWN actively considers whether the stated problem is the right one, or if the actual bottleneck lies somewhere else.
TWN's contribution stood out in five key areas:
- Understanding the business challenge
TWN did not simply execute technical tickets. The team immersed itself in the business process to uncover what the user's real problem was. - Offering technical possibilities
TWN brings extensive Atlassian experience to the table. This allows them to identify what is possible with Atlassian in ways the client might not initially be aware of. - Fast delivery capability
More complex tasks were delivered swiftly with TWN's support. This helped maintain development momentum and eased the workload on the ministry's internal team. - Agility during development
Ideas evolve as work progresses. TWN is prepared and skilled at incorporating these changes smoothly throughout the development process. - Bridging business and development
Workshops facilitated by TWN helped HTM build a shared understanding of what was being built and why. This minimised the risk of a technical solution solving the wrong problem.
The Atlassian platform provides HTM with the tools. TWN's role is to help make those tools work in a way that supports real users, real processes, and real management needs.
"TWN truly immerses themselves in the business process. They strive to understand the user's real problem, offer different technical solutions, and challenge whether we are solving the right problem in the first place."
- Toomas Adson, HTM
Contact
Stay up to date with our news and exciting projects
We share stories about our work and clients, talk about new trends in design and technology, and introduce the people in our team. Our content is a mix of useful information, inspiration, and sometimes a good laugh.