View this Project on GitHub
Watch a video demo
description
Work Notes Clipboard is a one-click copy-paste command center I built in PowerShell when my team that needed to perform massive amounts of repetitive data entry tasks while not being keyboard savvy. You click a button, it copies and auto-pastes — no hotkeys, no switching windows. Tab-categorizes different topics. Includes a built-in income eligibility calculator for enrollment workflows. Built entirely by me, now generalized and open-source, Windows-only, runs off a single .ps1 file.
features
- Tab-based organization — categorize by topic (generalized examples include Git, Emails, Links, Snippets, etc.)
- Green/red button system — "Approved" vs "Deny" notes at a glance
- One-click copy + auto-paste — no CTRL+C, no CTRL+V, just click and it's there
- Configurable auto-paste delay — for slower/faster workflows
- Full tab & note editor — add, rename, reorder, delete tabs and individual notes. Configurations are saved in JSON files
- Built-in income eligibility calculator — PAYSTUBS tab takes pay period data + household size, computes approval thresholds on the spot (specific to its original job function)
- Settings — sort alphabetically or by most-used, font sizing, hover-to-switch tabs
- Persistent JSON config — everything saves, survives restarts
- Reset to defaults — one-click factory restore
results
Upon the completion of this project, it was made mandatory for my entire team of 40+ people. It drastically improved our quality assurance scores, boosted employee morale, and increased productivity. Additionally, it made onboarding new employees a breeze.
background
This was the first big project I headed in my career. I was a contacted employee at the time, and I was supporting a small government startup on the operations side.
My job role was more data entry than systems analyst, app developer, or anything like that; however, I couldn’t help but notice how many inneficiences were bogging down my team. There was a specific bottlenck that was especially frustrating— the team needed to type very specific codes into Service Now for each ticket. This isn’t that bad, but there was about 30 of these notes, and much of our team was techincally inexperienced and slow at typing.
After our team had tried and exhaused many possible solutions (handing out paper packets with the codes, trying to teach people how to use sticky notes, and using Windows-V) we ultimately came to the conclusion that there was not an elegant solution for our needs that didn’t involve the purchase of external software at scale.
Having limilted experience with scripting, I experimented on my own machine with Powershell shortcuts that would auto paste some of the most common codes. This worked well enough, but I knew this wasn’t a scalable solution. After a few days of tinkering, researching, and testing, I proposed a fuller solution to my Director. He was totally on board, and granted me the privilege and resources to build.
I first conducted interviews with our director, our manager, our supervisors, and most importantly our people on the ground to build requirements for the solutions. Additionaly, I shadowed several members of the team to get a real sense of how they worked, whether they used the mouse or keyboard, and where their eyes were drawn when processing a ticket.
Once I had my requirements, I began to build. I took a Continuous Integration and Continuous Delivery (CI/CD) approach— initially building a minimum viable product (MVP) and iterating based on feedback. This allowed me to show progress while highly integrating user’s wants and needs. Throughout the development, I would send out “beta” versions of the product to different team members for additional feedback, which proved invaluable. The finished product was done in roughly 2 weeks, and was substantially more robust than I had initially planned, while avoiding major feature creep.
main page
tab edit menu
page edit menu
settings
reviews
I promise more people than just Mary liked it, but they didn’t comment on my Linkedin post