In this meeting segment, Mike Lyons, Michelle, and another participant discuss the wording and functionality of the button that appears in the AskMe virtual coach interface. The current button displays agent‑specific text such as “Ask Mike” or “Ask Michelle,” while the surrounding instructional copy suggests the learner should “click submit” for the coach to review their work. This mismatch creates confusion for learners and has drawn criticism from an instructional designer. The team debates whether to keep the button, rename it, or remove it entirely. They conclude that removing the static HTML button—since it does not perform a distinct submit action—will simplify the UI and avoid learner uncertainty, with a plan to eliminate it from future builds and retroactively from existing versions.
Chapters
Is it redundant or should we just, you know, people get that they click the submit to ask Mike?
Well, yeah, Michelle, what problem were you trying to solve by not having it there?
Because it says your, your instructor will review your work and provide coaching feedback. It sounds like I'm actually going to, me, myself, going to review the work and then send them an email or something.
Right.
Yeah.
So it's like, uh, when you click submit, your virtual coach, Ask Michelle, will review your work, right? Yeah. I think, I think probably taking it off solves the problem for everybody. What do you think, Michelle? Think about it from a product perspective for all instructors. Would you think it should just not be there or should, what do you think?
I mean, I get, I get that's what you were going with. Um, I totally see that. I think the wording, like, I don't know how it's worded in the beginning, like the ask me or like ask Mike, or, or I don't know how, how you would phrase it that way somehow. Um, 'cause you don't want to say like, you know, what's substituted with whatever your agent name is. Yeah.
Let me, let me add another little nugget of like problems. Um, the button doesn't actually say submit to on any of mine. It just literally all it says is ask Mike. So I already got a comment from somebody that says, what submit are you talking about? I don't have a submit. I have a button that says ask Mike.
So if we got rid of it, that wouldn't hurt. That, that's the easy button, to be honest.
It is, but does then the learner/student know that they're supposed to hit the button that says, ask Michelle?
Yeah, that's true. That's valid.
But yeah, let's take it off and see if the problem arises ever again. Yeah. I mean, that's Michelle. That's how we, like, that's how we decide.
If it works for y'all, keep it. I'll just refine it or I'll try to redo it. For me, it was just a little—
No, no, no. I think we have to do something because I got this feedback from an instructional designer at the school. It was the only thing she said. She didn't even say, hey, cool responses. Like, hey, come on. She's, that's what she told me. It's like, oh my God.
Yeah. Okay. Let's continue though. Sorry for derailing. I just thought about this and while you were doing this, I wanted to bring it up.
That's a great one. And what I can do is we could get rid of it in all future builds and then just sort of ripple through the existing ones and get rid of it. Because it's just, it's just a piece of HTML sitting in there that doesn't do anything.
