Stop Searching for Documentation: Why We Stripped the Settings Screens from Rizm

#productivity #ai #showdev #management

Whenever a team adopts a new tool, an invisible burden is created: the dependency on a "tool specialist."
We've all seen it—people spending hours learning proprietary specs or even getting "admin certifications" just to manage a workspace. We want to change this culture of wasting time on tool-specific mastery.

Our project, Rizm, takes a radical approach: minimize settings screens and embed management best practices directly into an AI layer.

Eliminating the "Search for Settings" Time

In Rizm, you won't find complex nested settings menus.
It’s built on the design philosophy of "Data × Manifest = UI." Instead of manually toggling switches, you simply tell the AI how you want to work, and the AI rewrites the workspace configuration itself.

For governance, configuration changes are still restricted to Admins. However, those Admins no longer need to memorize "which switch does what."

This is made possible by a mechanism we call AIT (AI Transformation).

Letting PMs and Devs Manage Without the Overhead

In traditional tools, a simple configuration change requires specialized knowledge.
In Rizm, an Admin can simply say, "Add a new field for 'Reviewer'," "Clean up the board view," or "Enable the GitHub integration." AIT then reconfigures the workspace based on those natural language instructions.

Since the learning curve is nearly zero, PMs or engineers can handle admin tasks as a "side-hustle" with minimal effort. There is no longer a need to train or hire a dedicated "tool craftsman."

Two AIs, Two Roles

To keep things organized, we divided the AI's responsibilities into two layers:

AIT (Configuration): The "Architect." It builds the system's skeleton—adding fields, organizing views, designing statuses, and enabling integrations based on Admin input.
AI Assistant (Operations): The "Assistant." It supports daily tasks for all users by reading existing data to draft Wikis, investigation logs, and release notes.

Building an Adaptable Foundation

You don't need to define everything perfectly from day one.
As your project evolves, you can refine the workspace through simple conversation. Tell the AI what you need, and it will fill in the gaps to reach the optimal setup.

We are building Rizm to be a flexible, autonomous foundation for teams—one where you never have to "adapt yourself to the tool" again.

Use Case Examples

Category	Type	Request (User Prompt)	Result (System Action)
Field Management	AIT	"Add 'xxx' to the country property."	A new property item was successfully added.
View Optimization	AIT	"I don't need the 'backlog' view."	The backlog view was removed from the workspace.
Config Cloning	AIT	(During new project creation) "Use the same configuration as the 'test' project."	Replicated the existing project's structure for the new setup.
Workflow Design	AIT	"Add 'Closed' to statuses, but don't display it as a board column."	Added the status while keeping the board UI clean as requested.
SCM Integration	AIT	"Integrate with Bitbucket: `https://bitbucket.org/user/repo`"	Set up integration. Successfully parsed repo details directly from the URL.
User Admin	AI Assistant	"Add `test8@x.com` as an editor and assign them to Team1."	Handled user creation and group assignment via chat.
Data Logging	AI Assistant	"Analyze weekly completion rates and save the results to a new Wiki page."	Generated the report and automatically created a Wiki entry.
Release Notes	AI Assistant	"Check tasks labeled 'beta8' and draft release notes in concise English, following the style of 'beta-v7'."	Parsed task data and generated consistent release notes based on past entries.