Our Process
Together, this is how we’ll build your operations system
Phase #1
Before building anything, we collaborate on modeling your organization’s activities to form a set of project blueprints, including a vocabulary (one of the two hard things in computer science, as the saying goes, is naming things).
Because our basic unit is the business operation, we refer to our method as BOND (Business Operations Notation & Development). Within BOND we practice what we call Role & Port Modeling, as these are the twin aspects of a system: Roles for who can do what, and Ports for where they do it.
To capture ideas for the blueprints, we enter them into the Engaging OS platform itself, fulfilling one of the holy grails of software: being an executable model.
Phase #2
Engaging OS imposes some design constraints in that apart from public-facing ones, there are only two main types of screens: 1) role dashboards, comprising sets of consoles each likely displaying a table; and 2) ports, likely being forms. Within these constraints, we express and build on your brand, striving for elegance.
We value consistency. Luckily for our medium, consistency makes a software system not only easier to use but also easier to produce.
Ultimately, we hope to achieve personality, which can emerge with consistent use of a critical mass of design patterns.
Phase #3
If we are not extending your current system but migrating your data to a new one, we perform that by configuring an established import script. This makes the import easily repeatable.
To replicate the relations between entries despite any differences in data architecture, we migrate all entry ids from the old system, which the script utilizes to relate our new tables.
The migration script perform various checks, such as avoiding repeatedly remigrating unchanged files.
If your organization already manages people in a payroll, HR, CRM, or AMS system, we integrate with it to stay synced.
Phase #4
Development proceeds according to the order determined during Phase #1, based both on your business requirements and on which aspects of the system depend on others.
We meet regularly with relevant members of your organization for them to evaluate progress, provide course-correcting feedback, and learn about the system. The frequency of these meetings depends on the nature of the current work, varying from weekly or more to bi-weekly or monthly.
Phase #5
During the intense pre- and post-launch periods we observe each and every user session—there’s nothing better for revealing and addressing user confusion.
Phase #6
Emerging from the post-launch period, we’ve only reached the end of the beginning. As your organic system grows, we are with you for the journey.
Capacity
We can onboard more organizations next month.
One Small Step
Tell us about you and your organization