@ColoKate63 wrote:
You all need to start using AI to frame out your Coyle reports.
I find this questionable for a variety of reasons...outside of the fact that it would most likely start providing redundant narratives that will ultimately have you flagged and removed from their system. If an AI system were to work for us, the editors are probably soon to be replaced by, or at least utilize, an AI that will probably spot your AI generated content.
1. The examples are of one particular, and basic, experience, and it's not as much of a cookie cutter process as one might think. What happens when the server brings the wrong entree to the table, or spills your drink, or the check is wrong, or another server takes over mid-meal, etc. None of that is contained in the sample narratives, so it has to be spelled out. There is no way for the AI to know the specifics of your dining experience unless told, so you are either spending a LOT of time doing that, or submitting fallacious reports.
2. The reports are sectionalized, so you would have to either create a doc that has all the sections combined, and later split them out again, or do this process over and over for each section. And different clients have different standards, and different sections. Some additional narrative sections are now required inside the questionnaire, so you could have upwards of 20 narrative sections in a dining report.
3. 50% of the time I spend on Coyle reports is scanning and uploading receipts, filling out the checklists and answering the comments related to that, which an AI is most likely not yet doing for you.
Based on your claim of being 75% done when the narrative is written, I'm guessing perhaps typing is your biggest time investment. I can start and finish a dining report in about an hour when typing it myself. I find that to simply be the fastest process, and I am an average typist. What is your typing time when typing it yourself, and what it the average time to generate the needed AI content, and then proof it to Coyle standards?
I probably have completed more dining reports for Coyle than anyone in their system. That accounts for part of my speed, because I know the system well, but since I have been doing it for more than 20 years now, I have tried countless ways to speed the process up. The second fastest way I found was being able to generate narratives using speech to text software, but the editorial and formatting fixes that were required always bogged me down. I could see AI helping with that if you could develop a Coyle format template, so I'm guessing it might save you a few minutes of time, but in the end, you still have to know the standards and system to utilize that process.
That said, what's the big issue with just learning the standards, going for dinner and then sitting down and banging out a report the old fashioned way. They way that was intended, and that you are being compensated for? This work is about reporting on human interaction, from the point of view of another human. That's a core element of "hospitality". Once you start injecting AI into that chain, I think it breaks down pretty quickly and we end with AI monitoring service through cameras at the restaurant, and generating reports that render us useless.
I've spelled out my process in many different threads here before, but the basic component of it is just having an organized, ergonomic work environment. Coyle does not require a novel. Looking through my last 10 dinner assignments, they are between 3-5 pages of written text in a 12pt word doc, or about 1,000 words. Google tells me the average time to type that out is 25 minutes.
I take detailed shorthand notes at the restaurant, email them from my phone, and then just have that email side-by-side with a word doc that type into. 20-30 minutes for that, then proof against the checklist, upload the receipt and done in about an hour. If it's taking you more time, perhaps there are other components you can work on to improve your speed that will carry over into all of the work that you do.
BTW; I understand the inclination to automate. I just don't always agree with it. I have an assistant who's younger than me, and obsessed with automating everything in the workflow at my main job. I had a project that was particularly redundant and asked him for help with it. He developed a script that saved a few days of my time, which was great, but he continues to try to automate every aspect of his job, including having AI reply to his emails, and a variety of other client-facing elements. My client called me recently and said they would prefer if I took over attending meetings for the project I had assigned to him. The work he was submitting was good quality, but the client's team had lost faith in him from some of the responses they received when interacting with him. I can chalk some of that up to experience, but I feel like the lesson here is knowing when automation is helpful (for redundant mindless tasks) and when human interaction is important. I have no issue using automation to resize or rename a batch of photos for a hotel report. I just think Coyle's end client is probably more interested in your personal subjective commentary that whatever an AI can regurgitate.
Even if Coyle now indeed does suck to work for, I still take pride in the work I do. If a lower myself to their level of apathy, the work ultimately suffers and the end clients will see that, and there goes my 'free' dinner...