At some point, in almost every company, someone asks: "Do our values actually matter?" It's a fair question.

On paper, everything usually looks right – the wording is thoughtful, the intent is clear, and no one really argues with what's written. But if you watch how teams actually operate week to week, values rarely come up.

People don't reference values in standups, don't use them to resolve disagreements, and don't think about them when deciding whether to push back on a deadline or ship something that isn't quite ready.

As long as things are going smoothly, it's all fine and easy to assume values don't really matter.

Change often occurs in challenging environments, and this is where sudden problems can become very real.

When priorities collide, timelines compress, or something breaks with no obvious fix – this is when values stop being abstract. In those moments, people stop looking at the handbook and start looking at what's actually happening around them.

For a developer, the questions get pretty specific:

• Do we protect quality even when the PM is pushing to ship?
• Can I flag that this architecture decision is going to hurt us in six months – or is it safer to just close the ticket?
• If I take ownership of something, and it doesn't go perfectly, will that be held against me?

Whether anyone names them or not, values are already answering those questions. Just not as words — as behavior.

The gap no one talks about

Most companies don't struggle to define values. The hard part is the translation – turning a slide into something that actually shapes decisions on a Tuesday afternoon when there's pressure from every direction.

You can usually see the gap in small things: What gets rewarded? What gets quietly ignored? What becomes acceptable when things get tight?

Culture doesn't live in how values are described. It lives in what happens when the answer isn't obvious.

What changes as a company grows

In a small team, alignment is almost automatic. Everyone's in the same room, decisions are visible, and context travels fast; as the company scales, this breaks down.

Decisions are suddenly happening in rooms you're not in. People are working with different information. Some engineers understand the "why" behind a product direction; others are left guessing, which leads to drift and second–guessing.

More processes don't fix that. What actually helps is a set of principles people can apply on their own, without needing someone to explain every call. This is when values stop being decorative and start being useful.

What strong values actually do

When they're working, values don't feel like rules; they feel like clarity; they don't remove complexity – they make decisions less arbitrary.

For someone building software, this matters in very concrete ways:

• Is this good enough to ship, or does it need another pass?
• Should I raise my concerns or trust that it's been thought through?
• Is this the kind of place where "done" means done, or done–ish?

Good values give you a consistent answer to those questions – not from a manager, but from the culture itself.

A quick way to check if values are real

Think of a recent situation at your current or past company where things were genuinely unclear or under pressure, then ask:

• Which decisions were implemented?
• What behavior was supported?
• What outcome got accepted?

Compare the answers to these questions against what the company says are its values. If the answers line up, those values are real; if they don't, they're still aspirational. There's nothing wrong with aspirational, but it's worth defining which one you're working with before you proceed.

What this looks like at Smart State

At Smart State, we drive businesses through smart engagement solutions and emerging tech. Our six values aren't a branding exercise; they're the answer to the preceding questions.

Always Deliver Quality – Means we don't ship things we're not proud of. When a timeline is tight, it creates friction — we've decided the friction is worth it. Every solution we build must perform — not most of the time, every time.

Adapt Quicker & Smarter – Clients change direction, markets shift, requirements evolve. The "Smarter" part is navigating all of this without leaving your team behind. It should be fast — never chaotic.

Embrace Emerging Tech – We pay attention to what's coming, not to follow trends, but because better tools make for better products and better experiences for the people using them. If you want to work with modern stacks and approaches, Smart State is built for that.

Put People First – In practice, this means a space where you can say something's wrong without having to manage the reaction; where feedback goes both ways; where creative risk is supported, not just tolerated. This is harder to build than it sounds, and it's something Smart State actively protects.

Operate Efficiently – Disciplined, not just fast, attention to detail. It’s the kind of environment where small issues are caught before becoming big problems.

Bring Your Bold – This one matters to us most. Smart State wants engineers who take full ownership of decisions, of outcomes, and of the work; not just when things go well. If you're the kind of person who raises a concern before it becomes a crisis, proposes a better approach even when nobody asked, and stands behind your calls — you'll fit in here perfectly.

Values don't come up much when everything's running smoothly; they appear when it's least expected.  By the time you need to know what a company really runs on, it could be -too little- too late to fix it.

If you're evaluating where to take your next role, it's worth thinking about it before you sign.