i’ll do my best!
i’m not licensed for Obsidian at work but i do have a few vaults including my own research data available on my employer-provided workstation and i can tell you how my workflow would be if i could go all-in on it.
my function organizationally is a critical component and aligns with four? other teams. we had to do a hard pivot march 2020 and had to use what we had or could quickly get. my source of truth i’m actually working from during our workshops are a OneNote notebook for each workshop mapped to ticket in ServiceNow. our workshops are held on MS Teams.
i’ve been writing in markdown for years and so it’s not really going to cause any big disruptions if/when i can get the appropriate license, there are at least five other people into this idea because i created an obsidian teams channel and four other people in there say hello. but because i am constantly writing in markdown (even in Outlook and MS Word 
) i have a set of markdown documents that are essentially templates i use and that i’d continue to use in an obsidian vault. i follow vaguely zettelkasten conventions (i always stamp new documents/files YYYYMMDDHHMMSS-$whatever for example) which i do use for each workshop. when i am done i re-write my actions and findings for submission into the markdown doc i created to prep and stage the workshop.
those notes are essentially my worklog but it’s all replicated effort right now. i index the folder with DEVONthink to an unsynced database on-disk (but outside OneDrive’s clutches) and can easily recall nicely formatted details about every workshop i’ve facilitated and very much look forward to a day when i can stop doing it twice. some of the things i could do with obsidian that would be amazing are not likely going to materialize for me however.
for example, if i were allowed to have an API credential for SNOW i would automate t-F out of staging and even committing findings and actions back into SNOW. that would make my life a lot better, but so would having an intern that would attend my workshops and do those things for me since they’re the only part of my job that i don’t find delightful.
edit: wanted to add:
during that staging/prep time in a markdown doc for the workshop i also bang out all the front-matter (i use the usual things (tags,date,title,id) but add: onenote-uri and snow-uri and ticket-id) and then i take all the gathered intake information, fill out my sheet (description, scope, SDL team, contacts ([[Person Name]]) and if i could i would have those notes of people contain a function to return/embed a list of all the workshops i’ve had with them, and/or findings that are open if i were allowed to use the SNOW API.
there’s a lot of untapped potential in my use of Obsidian. it’s pushing me towards Dendron and reverting back to research data in DEVONthink databases.