Adopting AI: From Improving Existing Tasks to Rethinking How We Work

Adopting AI: From Improving Existing Tasks to Rethinking How We Work

I Built an HR Knowledge Assistant and a GenBI Assistant. What Comes Next?

I’ve built quite a few AI agents and workflows, including an HR knowledge assistant and a GenBI assistant.

The HR knowledge assistant uses RAG to find information in HR documents and answer questions. The GenBI assistant uses Text2SQL so people who don’t write SQL can query data themselves, using everyday language.

The goal is straightforward: spend less time looking things up and doing repetitive work. But as I worked on these assistants, I started wondering what happens after someone gets the information.

With GenBI, someone might use the results to prepare a report for their manager. They might also keep asking questions and explore the data further. The first use helps them finish an existing task faster. The second could help them pursue questions they previously left unanswered because they couldn’t query the data themselves.

That reflects two expectations I’ve seen in companies. Some people want AI to take over work they don’t enjoy. Others want to try things that used to be too expensive or impractical. The same tool can serve both purposes.

Automation has been around for a long time. Tools such as n8n and RPA can already handle plenty of repetitive tasks. When AI enters the picture, I’m more interested in what else it enables people to do.

In my own experience, saving time with AI hasn’t led me to do more work. If I measure productivity by the amount of work I finish, it hasn’t increased much. The clearest benefit has been the time saved. That also makes me want to look further: do these changes help the team get more done?

Employees Deliver Faster. There’s Still Only One Manager.

Daren Academy’s Small Talk, EP715 describes a familiar situation: an employee saves several days of work with AI, submits a proposal, and still has to wait until the following week for their manager to review it. As everyone submits more work, faster, the manager still needs time to read it, find problems, and send it back for revisions.

So even if employees spend all the time they save on doing more work, they might simply add more proposals to their manager’s pile.

Daren Academy’s Joe suggests making experienced managers’ judgment criteria explicit, so the team can use AI to check work before submitting it and reduce revision cycles.

That made me think about turning those criteria into a skill: instructions and reference material an agent can use while doing a task. Employees could document the steps they know well. Managers could document their review criteria: what information must be included, which conditions would cause a rejection, and which situations need a person to decide.

This is my own extension of the discussion. Run the checks that can happen earlier, then leave the trade-offs to the manager. The criteria also need to be adjusted based on actual results, including any problems they fail to catch.

Tech.wav EP160 also discusses trust in agents. Host Harry recounts Lauren Tan’s experience: she could ship thousands of pull requests in a single month, and even product managers and designers on the team could use agents to contribute to production features.

Harry explains that Lauren Tan put effort into cleaning up the codebase and removing bad practices, then added automated checks, skills, and verification mechanisms. Together, these created an environment where the team felt comfortable relying on agents. That makes me think we also need to take care of the environment in which agents work when we hand tasks over to them.

Looking back at the HR knowledge assistant and GenBI, I want to check a few things too. Are the documents and data definitions clear? How should answers and query results be verified? Getting these things right could reduce the need for someone to watch every step.

When the Tools Change, the Way We Work Can Change Too

An article on ihower’s AIhao AI Engineering Blog discusses Walmart’s adoption of computers. It describes how sharing data in real time allowed stores and suppliers to make decisions using inventory information, changing how they replenished stock and worked together.

The example made me think that when information becomes easier to access, the division of work can change along with it.

GenBI helps people cross one barrier by letting them query data without writing SQL. But once they have the data, what can they handle themselves, and what still needs to wait for a manager? That part deserves attention too.

I recently heard about business process reengineering: starting with the outcome we want and redesigning how the work gets done. Applied to my own work, that means laying out the process and asking: which steps can we remove? Which checks can happen earlier? Which decisions can be delegated so the work can keep moving?

I can imagine companies with hundreds or thousands of agents taking on many of the tasks we do today. If every task they finish still needs approval from the same manager, today’s bottleneck will only get worse.

Along with turning tasks into skills, we need to decide how agents hand work over, when they should involve a person, and who handles problems. People need to work those things out first.

What Should We Do With the Time We Save?

I’d like to hand over the work that can be automated to agents, so people have time to focus on what agents still can’t do for us, especially communication.

When working across departments, having the information ready doesn’t mean the other team will agree to help. Each department has its own goals and priorities. You need to understand what matters to them, explain why the work is worth doing, and persuade them to commit time and resources. You still need to have those conversations yourself.

The same goes for getting support from your manager and explaining the direction to your team. Agents can help prepare information and organize what you want to say. But addressing people’s concerns and working out an approach everyone can accept still takes people’s time.

Agents can help analyze options and lay out the pros and cons, but we still need to decide what to choose, what we’re willing to give up, and which risks we’re prepared to take. We also have to take responsibility for the outcome. Those trade-offs can’t all be handed over to an agent.

Looking back at the HR knowledge assistant and GenBI, I’d like them to save people time searching documents and querying data, leaving them more room to use that information to discuss problems and move things forward. That’s what I want to keep thinking about: once an assistant finishes its part, how do people take the work further?

Hand over the work that can be automated to agents, and use the time saved for communication, coordination, persuasion, making decisions, and taking responsibility for the outcomes.

References

  1. ihower / AIhao AI Engineering Blog
    “Stop Reading AI Predictions: Cedric Chin’s Sensemaking Trilogy on Making Sense of AI”
    Article in Chinese
  2. Daren Academy’s Small Talk, EP715
    “AI Saves Employees Three Days of Work, but Their Proposals Sit on a Manager’s Desk for a Week. Why Does the Process Still Get Stuck When Everyone Is Faster?”
    Apple Podcasts, in Chinese · YouTube
  3. Wikipedia: Business Process Reengineering
    Entry in Chinese
  4. Tech.wav EP160
    “Companies Will Change Completely in the AI Era: How Can One Person Create a Hundred Times the Value? Anthropic and SpaceXAI Offer a Glimpse”
    Apple Podcasts, in Chinese · YouTube
Share :