Nice.
Thank you.
It's day two on Legends of Low Code.
All three teams have hit their laptops
running here at Fort Mason Center
to create an intake solution
for specific clinics
formerly known as Uplift Family Services.
This is a almost unrealistically short
amount of time to build an app in,
but that's the beauty of this challenge.
It's
a big ask for the entire
process lifecycle.
I would say the odds of my team
winning a probably one out of three.
All right.
Can I have everyone's attention, please?
Trailblazers.
Welcome to day two.
I hope you all got a little bit of rest
because this would not be a reality show
if we didn't throw
a wrench into everything halfway through.
Eleanor here has a
little bit of news for you.
Good morning, everyone.
Last night, we realized
we needed to add a validation process.
While we love automation,
we need our managers to have eyes on key
pieces of the process.
Low code is a very quick way
to build a system,
and it also means a lot of agility
for changing in the future,
which is key know
as we've all seen
with the pandemic, our ability
to like add a new form
into your onboarding process
overnight is really a
high value capability.
So I ask that you add
that workflow into your app
that will allow our managers to again
officially enroll kids into our program.
Now, don't panic.
You're all going to get a few minutes
with Eleanor to ask her
follow up questions about this
here in just a little bit.
Oh, looks like they're looking for
some sort of approval process,
which we can do out of the box.
So we'll definitely get a considered.
Emergency contact,
a birth, an emergency contact,
and then you can date of birth,
have that come back in
somebody review it, approve that,
and then they can be enrolled
in their programs.
The contact will be pretty much
who we're gearing it towards,
whether it's the parent
for a housing program
or a child for a behavioral
therapy program. Yeah.
So how about we add activity
tracking and chatter for case manager
collaboration on an intake, if you like.
That's a really good idea,
but I feel like we're getting to a point.
We're going to run up
against time deadlines.
We may have more
things than we can implement.
This deadline is no joke.
And now a serious
San Francisco storm
is raining on our Trailblazers parade.
So we have no Internet, at least.
Lisa, and I don't.
Nana is single handedly
carrying the team right now. Right.
My wifi is very slow.
Is it because of this wind or what?
Still loading.
This is frustrating.
The one thing we need is internet I know.
This weather outside is crazy.
Do we need to do our deep breaths again?
All right, let's do it.
Everybody in
and out.
Yeah.
Does that feel better?
Rain or shine presentations
aren't far away.
Hi, team.
How's day two shaking out?
Pretty good.
We did get a monkey wrench thrown.
Thrown in. Sorry about that.
Eleanor made me do it.
It's all right, it's all right.
But like we were saying,
that's pretty typical software
development process.
The requirements change,
you adjust and you move on.
If there is one thing you had to
you learn from and would do differently,
what would it be?
Not start building quite so fast.
We were really worried about the time,
so we just started building
and there was a point
where we were all working
on different things
and we had to sort of
stop and come together
and decide who was
going to work on each thing.
So I think I would take a little bit
more time upfront to do the planning.
So I know you've been
putting a ton of time
into the building process.
Have you thought at all about the pitch
in the presentation?
We've been working
on the presentation all along
to make sure that everything
that we're building,
that we've got that message
and we can tell that story.
At the end of the day.
How are you accounting
for different users
having different levels of access?
We're controlling that
through unauthenticated versus
authenticated access.
That way, we're able to expose
just the child records
to the right parents
in the right organization because, you.
Know, the folks at Uplift
aren't going to just say like, oh,
somebody doesn't have Internet access.
I guess I'll just ignore them.
They're going to make the effort
to figure out how to get
that person into the program
no matter what.
So we need to make sure
that the system reflects
that same attitude.
It sounds like you're
using a lot of empathy in your approach.
You did a good job listening.
I was great to check in with them.
I still feel like with Team Adventure,
they're holding their cards
kind of close to their chest.
And so it's kind of hard to glean
like what really. Is going on in there.
And I have to say,
answering their questions,
they were the one group
that I think understood
the complexities of the referral stream.
Are they kind of an underdog
or are they trying to make us think
they're the underdog
so they can kind of
almost surprise us in the end?
What did you think
just about how Team Odyssey said
that they started
working on their presentation right away?
I think it's smart, right,
because they're already thinking
about their app in terms
of a story and a flow.
It'd be very dangerous
to leave the presentation to the end
because that's a big
part of the story you're telling.
So by addressing that upfront,
they're going to have
maximum chance for success.
It looked like they always
had a plan B of,
you know, when they got stuck,
they would move on to the next plan
and keep passing things around
so that it kept the movement going.
I thought that was pretty impressive.
And also, I saw Quest.
They mentioned we build too fast
and we had to come back and redesign.
And I think that's part of the 48
hour challenge, too, right?
You've got to make decisions right away.
And sometimes it's not the right call,
but you have to move.
I have to wonder, given Quest's
comment about spending more time
in the planning stage
rather than jumping into solution,
you know, that gave me a pause.
Did they already have something in mind
even prior to getting some clarification?
So I think it's a little bit of a
theme of wasted time here
and how to recover from wasting time.
What I didn't like about what Quest said,
though, is the way
that they recovered was, yes,
kind of resetting and thinking
about the overall arching solution
that really helps them
accelerate after that.
We'll have to see
how pans out in a couple hours here.
I feel great today.
We have a great product
that we'll be showcasing later
this afternoon for Uplift
Family Services.
What are we going to do about reporting?
I think that would be good
for Rick to do it.
My team is absolutely amazing.
We come from different backgrounds
and we have a range from four years
to 50 years of experience on our team.
It's been great working with them.
I feel a lot better.
Aligned on what we're going to demo now.
We're getting the UI
all prepped and ready
and the data prepared.
Phil again.
All right, trailblazers,
we've only got 20 minutes left.
I want to see you
clicking a little faster over there.
Why don't we do that?
Why don't we hide the section?
If you had the whole section, you would.
Do like a.
Graphic of 18
and like an arrow going down.
You don't have to read it.
You look at that
and you know, like reduction. 18.
These final moments
see each team on the cusp of greatness
and we'll put something else there
that says you can not do an intake
until the minimum requirements are met.
It's not the best user experience.
Winning this challenge
will take every detail
and every bit of hustle they can muster.
In a perfect world,
this app will allow uplift
to focus on the service aspect.
What's the impact?
What are those impact.
Points that we. Want to make about?
First opening is really important.
The first 15 seconds
when they're going
to make their decision.
Presentation time definitely felt
a lot farther away
this morning than it does right now.
Yes, trailblazers.
Just 10 minutes left in the competition.
Trying to bring a project across
the finish line is really tough.
In that. Sector.
But it's also just
a really amazing experience too.
And so just seeing the
trailblazers embrace
that is what this is all about.
Only being two days long,
there's only so much you can build.
So low code is actually that springboard
or that accelerator for teams
to come together and build
something really quickly.
All right, trailblazers.
I've got good news and bad news.
The good news is you're almost done.
The bad news is you have one minute left
to finish up whatever you're doing.
Great. So we're just.
We're faster, faster, faster and faster.
I'm grateful that we're still smiling
and laugh when you have.
All right. 47 seconds. 46.
Are basically asking the trailblazers
to walk in the shoes of our customers
has been absolutely inspiring
to watch them do this.
We're very positive
that it's going to be very good.
But we're also curious
to see how the judges are going
to, you know, take our presentation.
So the contest is a perfect example
where a little coach shines.
All right, everyone, stop
building and back away
from the keyboards.
We are finished.
Coming up, the teams
present their apps to the judges
who will walk away with $10,000
for their favorite charity.?
Find out
next time on Legends of Low Code.
What I'm really focused on
is the storytelling element.
One thing I'm really hoping to see
is some innovation in the way
people are capturing data.
The winner is team...