Back to how I work

Adaptability in practice

Adapting the workflow to the ecosystem

Keeping the operational goal clear while adapting the implementation between Microsoft and Google environments.

Workflow
Files & inputs

Shared Drive / Google Sheets

Use shared cloud files when a local-file workflow does not fit.

Automation

Google Apps Script

Turn repeatable file and tracker operations into a connected workflow.

AI-assisted steps

Google Workspace Studio

Use the ecosystem’s available AI workflow steps where they fit, instead of hand-wiring a separate AI API call.

Example workflow.

The workflow comes first

I have worked in Microsoft and Google environments. Changing ecosystems can change file access, sharing, and which automation tools are practical. A process built around local files does not always transfer directly to a cloud workspace.

My approach is to map the inputs, transformations, review points, and outputs again, then select tools that fit the new environment.

Use what the environment already offers

In a Google workflow, that can mean Shared Drive and Sheets for shared inputs, Google Apps Script for repeatable operations, and suitable Google Workspace Studio steps for AI-assisted work instead of a separately wired AI API call.

The point is a workflow people can access, understand, and maintain with the tools available to them.

An example from my experience

My résumé includes automating HR candidate intake: files placed in a shared folder become structured records in a recruitment tracker. This removes a repetitive copy-and-paste step.

The ecosystem diagram illustrates the way I think about tool choices. It is not a claim that every tool shown was used in the same production system.