Building a knowledge base in a startup with Unifize

The thing about working at a small company is that it's the you know, it's about relationships, both with your coworkers, but with your suppliers, with your customers.

Right. When you have your people, the importance of people over systems becomes much more important. There's always there's always that balance, right? You can work for these huge 80,000, 80,000 person companies like Raytheon, where you have a very clearly defined role. It's very rigidly boxed. You only know the information for your particular project that you need to know.

I mean, literally your design inputs don't tell you anything about what you're actually working on in some cases for for good reasons. At a startup, it is it is very much about, you know, what is my what is my working relationship with my quality engineer, what is my working relationship with my suppliers? Right. Because at the end of the day, for a small company they live and die on, on relationships.

As far as the that ties into compliance, I mean, the thing is that everybody has to hold everybody accountable, right? We don't have the overhead or the or the systems that accrue over time that a rigidly enforce a set of standards as determined by the company. Right. And, you know, regulations are written from, at least in my opinion, from the sense that if you're doing everything right, everything that you should be doing, if you're doing a good job, you know, you will be very close.

If not already compliant with most standards. There was very few gotchas I've seen there in a tripped up. But the key thing is, is that you need to communicate right? I don't have a walking corpus of, you know, ISO 60601 in my head, right? I can't know everything about it, but between all the people at this company we do.

And so being able to communicate clearly with each other and being able to have information in a way that's easily accessible, that is flexible processes, is it is the strategy that you need to maintain, Right? If you try to enforce a rigid system on a start, it's just not going to work. There's no way, right?

You you know, there are days where I'll put on more of a quality engineering hat and maybe I'll go audit suppliers.

There are days where, you know, in the old days I'd literally was building robots in back. I was the technician. So I think that, you know, tying it back to regulation and I guess to Unifize is that the system that we have with Unifize reflects the scale and size of our company and the fact that it's so adaptive and we've changed it several times over already as we've learned more how to use the system and as we grow as the company is, that's really, you know, what we need as a company