Who is the Intended User of Kuali Build?
Everyone. But hey, let’s be a little more specific.
Office/Department of Information Technology
Of course, IT can use Kuali Build to fulfill requests to digitize data capture and workflow processes more quickly. But, it’s more than that. Kuali Build can be used as an interface for other systems of record. University of Michigan has a cool algorithm that forecasts a number of university stats, but needed the input interface. Enter Kuali Build. The workflow posts the data in the form out to the algorithm through an API integration. Yes. Pretty cool.
Business Analysts and Offices
Many offices on campuses have their own Business Analysts and UX managers who can design and create forms and workflow solutions without needing to take the time of engineers who need to work on more complex problems.
Colleges and Departments
We’ve discussed enabling quicker responses by IT/IS and increasing the number of personas who can build solutions. Let’s discuss providing a path for colleges and departments to own their own solutions—that democratization across campus everyone keeps buzzing about. They are being called “citizen developers.” Well, with so much critical and sensitive data at stake, we still need to be cautious, careful, and thoughtful. But, we can offer a path—a way to overcome the backlog—the hidden backlog.
We’ve found that colleges and departments often don’t even bring their latent needs to IT/IS. We call this the hidden backlog—all those forms, lists, and records that departments have not yet requested—data sitting in file cabinets—unfiltered, unmanaged. PDFs and Docx’s still abound, waiting to be printed and filled-out. These departments/offices eventually seek out solutions of their own. They go rogue. We want to help provide an IT/IS vetted path for them.
Who is the intended user of Kuali Build? Everyone.
Article is closed for comments.