-: My name's Lacy Reinell,
and I'm the VP of Customer Experience for Logics,
so I handle all of our customer relations
and quality control for our software tools.
So Logics is a small software company
based in Huntsville, Alabama.
We build software for government contractors,
particularly productivity tools,
so things that handle their time-keeping,
travel and expense management, contracts management,
and pretty much anything that
they need to run their business.
So in the software world, it's making sure
that the software that gets out to production,
in front of the customer, is of the highest quality
that it can be, meets the customer's needs,
and actually solves their problems.
So government contractors have a particular set of problems
that are pretty unique to their industry,
and so it's my job to kind of really understand
what it is that they need and to make sure
that the software we're building is going
to meet those needs and is of good quality
and what they expect.
So, it starts with just first understanding our customer,
so getting to know what it is they do on a day-to-day basis
and really interacting with them to find out exactly
what it is that we need to build.
The other part of that is working with the software team,
or development team, to make sure
that we're putting in proper testing procedures,
and everything from unit testing
to front-end functional testing.
And then we even work with some beta users
to get their feedback, and I collect their feedback,
take that back to the Dev team,
and really I'm just kind of the liaison
between our customers and the Dev team.
So, a translator, if you will.
It starts with kind of getting either a request
from a customer or just knowing that there's another
feature that we have to build onto our software.
We usually have some sort of whiteboarding session
where we have several people in the room,
whether that be a couple developers and a couple people
that actually are gonna be using it,
and we just kind of work through some details about,
"Alright, tell me what you need."
And we talk about how difficult it will be
to build certain solutions to meet that need.
Then once we've kind of decided on a certain path ahead,
then it takes it back to the Dev team
to actually build out the solution.
And then it comes to me to make sure
that it meets our design standards,
our quality assurance standards, and all of those things.
Then we'll push it out usually to a beta user
or someone to test it and give us feedback.
And then depending on how well that goes,
it might go through another cycle of upgrades
before actually getting out to production.