Skip to content
Jaee Blue
Selected Work

Enterprise technology operations

Technology Operations & System Testing

Working in technology operations has given me a different perspective on how businesses function.

A system can look great during development, but that doesn't always mean it works the way people need it to once they start using it.

My work involves supporting user acceptance testing, identifying issues, documenting findings, and helping ensure business systems function as expected.

What I enjoy about this work is that it connects technology with real business operations.

  • ServiceNow
  • SAFe
  • Jira
  • Confluence
  • Excel

01

The challenge

When organizations make changes to their systems, even small updates can affect how employees complete their daily work.

Something that seems minor from a technical perspective might create confusion, slow down a process, or prevent someone from completing a task.

The challenge is identifying those problems before they become bigger issues for the people relying on the system.

02

My role

As a Technical Operations Coordinator, I support system testing, issue tracking, documentation, and coordination between business and technical teams.

My responsibility isn't necessarily to write the code. It's to help make sure the technology does what it's supposed to do from the user's perspective.

That requires attention to detail, communication, and understanding how different parts of a process connect.

03

Approach

When I'm testing something, I try to look beyond whether a feature technically works.

I think about how someone would actually use it.

Does the process make sense? Are the instructions clear? What happens if someone makes a mistake? And does the change solve the problem it was intended to solve?

When issues come up, I focus on documenting what happened, what was expected, and what needs further attention so the appropriate teams can investigate.

I believe good documentation can make just as much of a difference as identifying the problem itself.

04

Outcomes

Through this work, I've contributed to user acceptance testing, issue identification, and documentation that supports system changes and ongoing operations.

I've also strengthened my ability to translate business needs into clear findings that technical teams can use to investigate and resolve issues.

05

Lessons learned

Just because a system works doesn't mean it's working well for the people using it.

Technology should support the way people work, not make their jobs unnecessarily complicated.

I've learned that effective testing requires more than following instructions. It requires curiosity, patience, and a willingness to question whether something could work better.

It's a perspective I also carry into the technology projects I work on outside my primary job.