Planning a Deployment
An Indicative Timeline
Section titled “An Indicative Timeline”The time a deployment takes depends on how much work is needed. The three estimates below are indicative.
| Work needed | Estimate | Examples |
|---|---|---|
| Basic adaptation | About 4 weeks | Look and feel and language. Pathway pages (static pages on sectors and qualification pathways). Grounding in local labor market data, if the data is readily available. |
| Light customization | About 8 weeks | Changes to the career readiness curriculum. More extensive work on labor market data, where it is needed. Localization of the taxonomy. Changes to the format of the skills report. |
| Additional features | About 12 weeks | New features, such as voice chat, a help chat that is available throughout the platform, or menus. |
Work beyond this needs to be scoped before it can be estimated. Examples are gamification on the profile page, notifications, and a mobile app.
What Adds Development Time
Section titled “What Adds Development Time”Four kinds of request go beyond configuration and localization. Each adds design and development time and should be budgeted.
| Request | Examples |
|---|---|
| Changes to the layout | A different layout for the home page or the profile page, or a different page structure |
| New features | Features that do not exist yet, such as voice chat or gamification |
| New modules | A module with a new objective that no existing module can be adapted to, such as behavioral profiling |
| Integrations with other systems | A connection to a case management system or another service. Both IT teams need to understand each other’s systems and design the connection together. |
Decisions to Prepare
Section titled “Decisions to Prepare”The program team makes decisions in six areas.
| Area | Decisions and inputs |
|---|---|
| Branding and identity | App name, colors, logos, icons, illustrations, and partner logos |
| User access | Open registration or registration codes; Google sign-in; access through the web application only or also through chat apps |
| Content and legal | The user information to collect; the privacy policy, terms of use, and data protection policies |
| Hosting and integration | Hosting arrangement, web address, web analytics accounts, and any connection to existing systems or databases |
| Language | Target languages, review of translations, and a list of local terms for work and employment |
| Research and evaluation | Evaluation design, target metrics, ethics approval, and reporting requirements |
Who Needs to Be Involved
Section titled “Who Needs to Be Involved”A deployment is an iterative process of design, build, and evaluation. It involves the program team, government representatives, sector specialists, and software engineers.
Technical support is part of Tabiya’s model. To discuss a deployment, write to hi@tabiya.org.

