Tech Break by Friday

Who notices the unanswered enquiry, chases the missing details, and remembers the follow-up?

In this solo episode of Tech Break by Friday, I explore the invisible coordination behind everyday business tasks, and how to tell whether AI actually removes that burden.

Through an illustrative event-planning enquiry, we look at useful questions, structured information capture, consultation booking, and clear human handoffs. A faster reply is useful. But what happens to all the checking and remembering around it?

In this episode:

• Why faster task completion can leave the coordination burden untouched.

• What a useful customer journey looks like beyond an automated acknowledgement.

• Who handles exceptions, and how to include review and correction time in your measurements.

• A simple exercise to identify one workflow worth improving.

Try this: choose one recurring situation where you have to remember, chase, or check something. Write down what starts it, what information it needs, what a completed outcome looks like, and who handles exceptions. Then ask what you can remove before automating anything.

Inspired by Elena Verna’s post about what women should expect from AI: https://lnkd.in/p/dhFXxcgA

The business-workflow application is my interpretation. The event-planning example is illustrative, not a measured client result.

Narration generated with ElevenLabs using my authorized Vivi voice.

Tech Break by Friday: https://www.techbreakbyfriday.com/

AureliaEdge: https://www.theaureliaedge.com/

A property manager already has a heating and cooling company she trusts. That company has serviced the building for years. There may be a maintenance contract, a history of repairs, and people who know the equipment.

Then a new automation sends somebody else.

The software has completed a task. The customer has a new problem.

That was the moment I kept coming back to after my conversation with Sally Hamidi, founder and CEO of ON Property Technologies, on Tech Break by Friday. Sally described a beta-launch lesson that reaches well beyond property management: before automating a workflow, understand the relationships and decisions inside it.

The assumption a beta customer challenged

Sally came to technology after years in HOA management, including owning and operating a management company. She knew what it felt like to balance inspections, board meetings, homeowner requests, and maintenance problems.

Even with that experience, she said her team initially overlooked an important customization: managers needed to choose their preferred vendors.

A beta customer made the gap clear. She did not want an unfamiliar contractor turning up when she already had someone responsible for that building’s maintenance.

Sally’s team responded by adding vendor preferences by trade and association. The lesson was specific. Existing service relationships were part of the workflow the product needed to support.

For founders, I think this is an excellent discovery question: What does your customer already know, trust, or have an agreement about that your automation cannot see?

The answer might be a maintenance contract. In another business, it could be an account owner’s approval, a customer’s communication preference, or an exception that has never made it into a process document.

Start with the delay that hurts someone

Sally used a roof leak to explain the operational problem she wants to solve.

A resident calls or emails. The manager is in a meeting or away from the phone. The message waits while the damage continues.

The opportunity is to shorten the path from a reported problem to someone taking action. In the workflow Sally described, a work order can be triaged to the building’s preferred vendor. The resident receives updates, the vendor communicates and documents the repair, and the manager can see what happened afterward.

This was an example of the intended workflow, rather than a measured customer case study. What made it useful was the clarity of the outcome: reduce time to resolution while keeping people informed.

When I look at an automation opportunity, that is where I want to start. Which delay is causing a real consequence? Who is waiting? What would a successful handoff look like?

A preferred vendor still needs a backup

Respecting a relationship does not mean waiting indefinitely.

Sally described a rule in which the preferred vendor gets the first opportunity. If that vendor is unavailable, the system can dispatch the job to other vendors in the area.

That gives the manager a way to express a preference without becoming responsible for every follow-up phone call.

It also makes the decision easier to inspect. You can ask who should receive the job first, what happens if they cannot take it, and what information the manager should receive.

Those are design decisions worth making before a workflow goes live. An instruction such as “find someone to fix this” leaves a lot of operational meaning unspecified.

Measure what happens on the job

We also discussed vendor accountability. Sally described several signals her team uses to understand performance:

* How quickly a vendor responds to a job.

* How many opportunities they miss.

* Whether they arrive and finish on time.

* How often they have to return to fix the same job.

* How industry professionals review their work.

The return visit matters. A job marked complete may still create more work if the repair was not done properly the first time.

My takeaway is to define success beyond the first completed action. For your own process, decide which signals show that the underlying problem was actually resolved. Track those alongside speed.

Keep the failure visible

Sally was candid about a beta work order that went to the wrong kind of vendor. A backflow-prevention issue was treated as a more general plumbing problem, even though the platform had a separate trade category for that work.

She said people still needed to oversee assignments. The system was not designed to be left entirely unattended.

That distinction matters when a workflow affects people’s homes. An automation can move quickly and still misunderstand the problem.

For me, this turns human oversight into a practical design task: decide who can see an assignment, who can correct it, and how the people involved will know that intervention is needed. Those are my implementation questions from the conversation, rather than claims that we verified every control inside the product.

A five-question check before you automate

Here is the checklist I would take into the next workflow discussion:

* What delay are we trying to reduce? Name the person waiting and the consequence of waiting.

* Which relationships or agreements must the workflow respect? Capture preferred providers, contracts, and existing responsibilities.

* What happens when the first choice is unavailable? Define the next step and the conditions for escalation.

* How will we know the work was done well? Include quality signals such as rework, as well as response time.

* Who can see and correct a mistake? Give a person the information and authority to intervene.

Sally’s advice to builders was to know the client, the pain point, and the details of the work. She also asked us to think about what a person gains from the product beyond time saved, including a deeper understanding of the problem.

That is a useful standard. When someone opens your system after a busy afternoon, can they understand what happened and what needs their attention?

Watch the conversation

Watch the Sally Hamidi conversation in the video above or on YouTube and subscribe for more practical conversations about technology, operations, and building businesses.

Connect with Sally

* Sally Hamidi on LinkedIn

* ON Property Technologies

* OnCall PRO

* ON Property Technologies on LinkedIn

Connect with me, Paraskevi Kivroglou

* LinkedIn

* AureliaEdge

* AureliaEdge on Instagram

Follow Tech Break by Friday

* Website

* YouTube

* Spotify

* Apple Podcasts

* Instagram

* Substack

If you want to put these questions to work in your business, start with an AureliaEdge Operations Audit.

Where has an automation missed something your team already understood? Leave a comment with your experience or a question you would like me to explore in a future Q&A video.

What does your AI strategy miss when employees choose their own tools? John Willis joins Paraskevi Kivroglou on Tech Break by Friday to discuss shadow AI, enterprise AI strategy, internal audits and who owns the results.

In this episode:

• Map the AI tools and workflows people actually use.• Support different levels of AI adoption across your organization.• Make AI audits useful for protecting the business.• Learn from failures to improve evaluations.• Give AI workflows clear ownership.

Guest linksJohn Willis at Dear CIORebels of Reason

Connect with the host, Paraskevi KivroglouLinkedIn · AureliaEdge · AureliaEdge Instagram

Follow Tech Break by FridayWebsite · YouTube · Spotify · Apple Podcasts · Instagram · Substack

Want to identify a useful first automation? Start with AureliaEdge’s Operations Audit. This is the host’s business resource, separate from John’s views and recommendations.

Listen to the full episode and follow Tech Break by Friday. Share your questions in the comments for a future Q&A.

What if privacy controls worked for people instead of interrupting them?Thede Loder, CTO and co-founder of Rewarded Interest, joins Tech Break by Friday to explain how personal consent agents can remove repeated cookie decisions, give consumers more control over identity, and share some of the value created when advertisers use better targeting signals.We discuss Thede's path from the early commercial internet and Match.com to anti-spam, digital identity standards, information economics, and consent for AI agents communicating with websites and MCP servers.Connect with Thede Loder:LinkedIn: https://www.linkedin.com/in/thede/Rewarded Interest: https://www.rewardedinterest.com/About the team: https://www.rewardedinterest.com/aboutConnect with the host, Paraskevi Kivroglou:LinkedIn: https://www.linkedin.com/in/paraskevi-kivroglou/AureliaEdge: https://www.theaureliaedge.com/Instagram: https://www.instagram.com/theaureliaedge/Follow Tech Break by Friday:Website: https://www.techbreakbyfriday.com/YouTube: https://www.youtube.com/@paraskevikivroglou7838Spotify: https://open.spotify.com/show/3c6KAQPQ54vxXUvLLRffC1Apple Podcasts: https://podcasts.apple.com/us/podcast/tech-break-by-friday/id1796711716Instagram: https://www.instagram.com/tech.break.by.friday/Substack: https://kivroglouparaskevi.substack.com/00:00 Meet Thede Loder and his path from the early internet to Match.com06:54 Why cookie consent creates an automation imbalance10:21 How Rewarded Interest makes money and rewards consumers14:28 The information economics behind better targeting19:15 Why AI agents need identity and consent controls22:08 Advertising in an agent-mediated internet24:37 Building a fairer internet for consumers31:33 Final thoughts and where to follow ThedeWatch the full episode and subscribe to Tech Break by Friday. Comment with a question you would like us to explore in a future Q&A video.

AI governance is not an abstract policy problem. It already shapes the products we use, the infrastructure we fund, the work decisions leaders make, and the relationships people form with AI systems.

In this episode of Tech Break by Friday, I speak with AD McSweaney about practical, human-centered AI governance. We discuss how to evaluate AI news, who carries the cost of data-center growth, why AI should not become an excuse for human decisions, what happens when models train on synthetic content, and where emotional support can cross into manipulation.

AD McSweaney and AI Governance, Ethics and Leadership

Substack: https://aigovernancelead.substack.com/

About: https://aigovernancelead.substack.com/about

LinkedIn: https://www.linkedin.com/company/ai-governance-ethics-and-risk/

Host: Paraskevi Kivroglou

LinkedIn: https://www.linkedin.com/in/paraskevi-kivroglou/

AureliaEdge: https://www.theaureliaedge.com/

Instagram: https://www.instagram.com/theaureliaedge/

Tech Break by Friday

Website: https://www.techbreakbyfriday.com/

YouTube: https://www.youtube.com/@paraskevikivroglou7838

Spotify: https://open.spotify.com/show/3c6KAQPQ54vxXUvLLRffC1

Apple Podcasts: https://podcasts.apple.com/us/podcast/tech-break-by-friday/id1796711716

Instagram: https://www.instagram.com/tech.break.by.friday/

Substack: https://kivroglouparaskevi.substack.com/

Continue the conversation: leave your question in the comments and subscribe for future Tech Break by Friday episodes.

Chapters

00:00 Introduction

02:22 What AI governance means

12:03 The EVA Index

16:09 Federal and state AI policy

18:38 Who pays for AI infrastructure

21:58 Environmental impact and efficient use

28:28 AI, jobs, and accountability

31:31 Human judgment remains essential

36:55 Trusting what we see online

38:53 What will AI learn from?

41:56 AI companionship and manipulation

49:47 Rebuilding human connection

52:18 Agent tools, security, and accountability

58:03 Closing

I tested Thinking Machines Lab's Inkling live across branding, website creation, code reasoning, general knowledge, and an enterprise compliance scenario.

Inkling is an open-weights mixture-of-experts model with 975B total parameters and 41B active. But scale is not the real question. The useful question is whether the model can follow instructions, explain its reasoning, produce practical work, and identify risks that matter in real applications.

In this episode, you will see:

- A general-knowledge answer checked against visible sources

- A coffee brand and interactive website concept created without image references

- The generated website's strongest ideas and its readability failure

- Inkling rejecting a hackish coding shortcut in its own reasoning

- A realistic SaaS compliance-assistant test

- Why auditability and context quality matter for production AI

- My verdict on using Inkling for product work and agent stress testing

Learn more about Inkling:

- Inkling overview: https://thinkingmachines.ai/inkling/

- Official announcement: https://thinkingmachines.ai/news/introducing-inkling/

- Model card: https://thinkingmachines.ai/model-card/inkling/

Connect with the host, Paraskevi Kivroglou:

- LinkedIn: https://www.linkedin.com/in/paraskevi-kivroglou/

- AureliaEdge: https://www.theaureliaedge.com/

- Instagram: https://www.instagram.com/theaureliaedge/

Follow Tech Break by Friday:

- Website: https://www.techbreakbyfriday.com/

- YouTube: https://www.youtube.com/@paraskevikivroglou7838

- Spotify: https://open.spotify.com/show/3c6KAQPQ54vxXUvLLRffC1

- Apple Podcasts: https://podcasts.apple.com/us/podcast/tech-break-by-friday/id1796711716

- Instagram: https://www.instagram.com/tech.break.by.friday/

- Substack: https://kivroglouparaskevi.substack.com/

Watch the full episode and subscribe to Tech Break by Friday. Leave your question in the comments for a future Q&A video.

## Chapters

00:00 Why Inkling matters

03:51 Architecture and benchmark tour

07:22 Tinker setup and controls

09:14 General-knowledge verification

10:52 Capella branding challenge

12:30 Website implementation and critique

21:58 Reasoning and code iteration

23:23 Instruction-following business case

25:21 Compliance critique and final verdict

27:40 Closing and viewer Q&A

AI can help us research faster, explain unfamiliar concepts, and move between technical fields more easily than before.

But there is a difference between producing an answer and understanding why that answer deserves to be trusted.

That difference became the heart of my conversation with Jennifer Tran, a technical writer and emerging-technology creator behind Realmscape. Jennifer has worked across web development, cryptography, and quantum computing. Her writing sits in a valuable place that is often missing online: between shallow marketing content and dense academic research.

Our conversation was not about rejecting AI. It was about using it without giving away the human abilities that make the work original, useful, and credible.

Join Skool and learn AI with a community of welcoming and ambitious individualshttps://www.skool.com/ai-advantage-club-5848/about

Writing is a test of understanding

Jennifer became more consistent with writing after recognizing two related problems.

First, people often hear about the impact of technologies such as quantum computing without understanding how those technologies actually work. They know the headline, but not the mechanism underneath it.

Second, she realized that knowing a subject at a high level did not always mean she could explain it with clarity. Writing gave her a way to slow down, examine the gaps, and organize the how and why behind a technical idea.

This is one reason writing remains important in the AI era. A generated answer can look complete while hiding weak understanding. Writing something yourself forces you to decide what matters, create a logical sequence, and explain the idea so another person can follow it.

It turns knowledge into structured thinking.

The missing middle in technical content

Technical information often appears at two extremes.

At one end, there is simplified marketing copy that tells us why a technology is exciting but leaves out how it works. At the other, there are academic papers and highly specialized explanations that require deep subject knowledge.

Jennifer writes for the people in between. They want more than a headline, but they do not need a PhD-level treatment of every subject.

That middle ground matters because emerging technology affects people long before most people become specialists in it. Developers, operators, founders, and curious professionals need explanations that preserve substance without becoming inaccessible.

Good technical content does not remove complexity. It gives the reader a path through it.

Use AI for clarity, not as a substitute for judgment

Jennifer described a practical approach to AI-assisted learning. She starts with foundations, including academic papers and credible news sources. When a concept is difficult, she may use an AI tool to help explain it. She then checks the explanation against the original research or the people behind it.

That makes AI a bridge to understanding, not the final authority.

The most useful question from our conversation was simple:

> What are you willing to delegate to AI?

This is more useful than asking whether AI can perform a task. Capability is only one part of the decision. We also need to ask what we might lose when we delegate it.

If AI drafts everything, do we lose our voice? If it performs all the research, do we stop checking sources? If it makes every technical decision, do we still understand the foundations well enough to notice when something is wrong?

Automation should remove work deliberately. It should not quietly remove judgment.

Trust comes from questions and sources

Jennifer’s approach to trustworthy content starts with the questions a real reader would ask.

What is missing from the usual explanation? What would a developer need to understand next? Which claim needs evidence? Who produced the original research?

She also emphasizes showing sources. This is especially important in fields affected by sensational headlines, weak summaries, and fast-moving claims. Naming where information came from gives the audience a way to inspect the path behind the conclusion.

Trust is not created by sounding certain. It is created by helping people see how you reached the result.

For creators, this gives us a practical standard:

1. Begin with a real question.

2. Use primary and credible sources.

3. Explain the reasoning between the source and the conclusion.

4. Separate what is known from what is still uncertain.

5. Make the work understandable without stripping away the substance.

Developers should create content

Jennifer believes developers and technologists are well positioned to help other people learn. They already encounter the practical questions, constraints, and tradeoffs that generic content often misses.

Creating content also benefits the developer. Explaining a system reveals where understanding is strong and where it is still vague. It creates a record of learning and can open a path into adjacent fields.

AI makes those transitions faster. Someone can begin in web development, explore cryptography, and then learn about the intersection of cryptography and quantum computing without waiting for a formal degree at every step.

The opportunity is not to pretend expertise appears instantly. It is to learn faster while remaining honest about the work required to verify and understand a subject.

What humans should protect

Near the end of our conversation, I asked Jennifer which human abilities we should protect as AI improves.

Her answer covered three areas.

Creativity

AI needs human ideas and new material. If people stop creating and only recycle machine-generated outputs, the result becomes repetitive. We still need original questions, stories, art, experiments, and ways of seeing the world.

Physical and mental health

AI can offer information or support, but it cannot take responsibility for how we live. Protecting our health, attention, and relationships remains human work.

Foundational learning

We need to keep learning how things work. Foundations let us adapt, move into new fields, evaluate outputs, and invent what comes next. If we lose them, we also lose the ability to challenge the tools we use.

AI may accelerate problem-solving, but humans still choose the problems worth solving.

A practical way to use AI without losing your edge

Before delegating your next task to AI, ask:

- Am I using AI to understand this better or only to finish faster?

- Which part of this task requires my judgment, experience, or voice?

- Can I verify the important claims using credible sources?

- Do I understand the foundations well enough to recognize a bad answer?

- What will I stop practicing if I delegate this every time?

AI is a powerful tool. The goal is not to keep every manual step. The goal is to make deliberate choices about what the tool handles and what remains yours.

That is how we gain speed without losing clarity, trust, or creativity.

Follow Jennifer Tran

- Realmscape: https://realmscape.substack.com/

- LinkedIn: https://www.linkedin.com/in/jennifertran-seattle

- Medium: https://medium.com/@jkim_tran

## Connect with me, Paraskevi Kivroglou

- LinkedIn: https://www.linkedin.com/in/paraskevi-kivroglou/

- AureliaEdge: https://www.theaureliaedge.com/

- Instagram: https://www.instagram.com/theaureliaedge/

Follow Tech Break by Friday

- Website: https://www.techbreakbyfriday.com/

- YouTube: https://www.youtube.com/@paraskevikivroglou7838

- Spotify:

- Instagram: https://www.instagram.com/tech.break.by.friday/

- Substack: https://kivroglouparaskevi.substack.com/

Watch or listen to the full episode and follow Tech Break by Friday for more practical conversations about technology and the people building with it.

What would you like me to ask Jennifer, or a future guest, in a Q&A video? Leave your question in the comments.

Most AI conversations jump straight to AGI. Ian P. Cook prefers a more useful question: how do we make today's AI reliable, measurable and valuable in the real world?

Ian is SVP of AI at Qloo, where he leads work around consumer-preference prediction across entertainment, fashion, dining and travel. His career spans startups, machine learning products, healthcare, insurance and government and defense applications.

In this episode of Tech Break by Friday, Ian cuts through the hype and explains what practical AI implementation requires:

- Defining the business problem before choosing the model

- Keeping humans accountable for high-stakes decisions

- Using AI to accelerate compliance and policy work

- Controlling LLM costs through focused context

- Designing fallbacks for outages and provider failures

- Turning expertise into repeatable AI skills

- Evaluating AI from both technical and business perspectives

- Understanding where current LLMs may reach their limits

Ian's message is clear: meaningful AI progress is built through measurable outcomes, responsible architecture and human judgment, not spectacle.

Ian Cook is SVP of AI at Qloo. Find him on LinkedIn as Ian P. Cook and learn more about his consulting and prototype work at https://fiercehighways.ai/.

CONNECT WITH PARASKEVI AND TECH BREAK BY FRIDAY

Personal website: https://paraskevikivroglou.com/

LinkedIn: https://www.linkedin.com/in/paraskevi-kivroglou/

Tech Break by Friday: https://www.techbreakbyfriday.com/

Newsletter: https://kivroglouparaskevi.substack.com/

WORK WITH AURELIAEDGE

Website: https://www.theaureliaedge.com/

Email: [email protected]0:00 Welcome and introduction

1:52 Meet Ian Cook and his AI product background

3:57 Why fast feedback matters in AI products

5:36 Where AI still needs human judgment

7:50 Using AI for SOC 2 and compliance work

13:08 Data storage, focused context and LLM costs

16:37 Designing reliable AI systems and fallbacks

20:36 Does learning to code still matter?

23:36 Why AI projects fail without problem definition

29:21 Try AI before you fear it

33:15 Why jobs are more than a list of tasks

35:48 AI skills make workflows repeatable

39:50 Evaluations, human review and building trust

45:19 AI hype, scaling limits and the road to AGI

50:19 Where to find Ian Cook

Today's my birthday, and before we get into the episode, I've got something special for you. To celebrate, I'm giving you a birthday gift: 50% off the paid membership, but only until tomorrow. If you've ever thought about upgrading to the podcast's paid content, this is the moment. Inside, you get a personal Q&A with me, plus the deeper content that AI-first people actually consume.💙https://kivroglouparaskevi.substack.com/1f1e7551

Join the Skool community here: https://www.skool.com/ai-advantage-club-5848

And if you want the shortest possible version once a week, subscribe to the 1-Min AI Newsletter.

Every week, I send one practical AI idea, tool, workflow, or case study you can understand in under a minute.

Subscribe here: https://kivroglouparaskevi.substack.com/subscribe

The company behind all these: https://theaureliaedge.com/

If you are building your AI infrastructure and you want help contact us, or visit the website a free goodie too.

➜ listen to the episode

✰ Website hub: https://techbreakbyfriday.com

✰ Newsletter & show notes: https://kivroglouparaskevi.substack.com

✰ Spotify: https://www.youtube.com/redirect?event=video_description&redir_token=QUFFLUhqbVVaYjBnZUpjenFRanAycUNIQklGUGtVWXZPd3xBQ3Jtc0tsdXhySFNnLU5PeU1DbXNYdnkyMkEybzFBcVdRSEpHMzNCeHBVNThQMzd2SnVaTnctTU5yaW9nakRHTEhrUHRRQ3RvNnkzMVBNU24xb045eG5OUm1CdTl0cmNseVBRWUxJUVdDRVdERnRLa0FyNVBTdw&q=https%3A%2F%2Fopen.spotify.com%2Fshow%2F3c6KAQPQ54vxXUvLLRffC1&v=Qjwp1LQOsww

✰ Apple Podcasts: https://podcasts.apple.com/us/podcast/tech-break-by-friday/id1796711716

What does AI-native insurance actually look like when humans stay in the loop?

In this episode of Tech Break by Friday, I sit down with Juan Garcia, co-founder of Tuio, to talk about how AI is changing insurance from the inside out. We discuss why the traditional insurance experience feels broken, where AI agents can create real value, and why the most important parts of claims, trust, and customer experience still need human judgment.

The company behind all these: https://theaureliaedge.com/If you are building your AI infrastructure and you want help contact us, or visit the website a free goodie too.

In This Episode

Why insurance is still such a broken customer experience

What it means to build an AI-native insurance company

Where AI agents can help in claims and customer support

Why humans still need to stay involved in sensitive decisions

The difference between useful automation and bad automation

How founders should think about AI ROI beyond headcount reduction

What non-technical founders can do to start using AI practically

Key Idea

AI-native does not mean humanless. It means knowing exactly where AI should speed things up, and where human judgment still protects trust, fairness, and customer experience.

New Segment: 1-Minute AI Concept

I’m also starting a new Tech Break by Friday newsletter section where I break down one AI concept in one minute.

Each week, I’ll take one idea from AI, automation, agents, startups, or business workflows and explain it in plain language so you can actually use it in your work.

Subscribe to the 1-Minute AI Newsletter by Tech Break by Friday for one practical AI idea every week.

Links

Follow Juan Garcia:LinkedIn: https://www.linkedin.com/in/juanga2/

Learn more about Tuio:Website: https://tuio.com/LinkedIn: https://www.linkedin.com/company/somostuio/Blog: https://blog.tuio.com/

Tech Break by Friday:Skool community: https://www.skool.com/ai-advantage-club-58481-Minute AI Newsletter & Substack: https://kivroglouparaskevi.substack.com/subscribeYouTube: https://www.youtube.com/@paraskevikivroglou7838