With your technical documentation, every company is a little bit different on how they do things. And obviously your goals are going to be different from someone else’s. So what I like to do first is talk to you about what you’re doing and what you’re working with. And I have a list of questions I always ask everyone going into that.
From there, after I get done listening to that, I can give you a very high-level overview of what I think needs to happen and why, which direction you should probably take on that. And if you want, we can then talk about the different options that you have. Now, I know if you’re a traditional corporation, you probably have a W2 arrangement involved.
And that can work, but usually, the way I do things, it’s not really -- I don’t know what the right word is. What I offer is a little bit cheaper in how I do things. So, I could still be on W2, but how we work together is going to be very clearly defined and very flexible.
And I’ll show you that as we walk forward with that. So we can look at polishing your existing documentation, we can look at your full information architectural analysis, and providing to you that detailed road map of everything that would need to be done down to the details -- I mean, down to a lot of detail, that would need to be then given to your project managers to fit into your sprints.
But the first step in all of that is really just to have a conversation. And I love listening to you guys about your documentation. So feel free to contact me through my website, and we can talk about booking a call. It’s usually not a problem. Okay?
Share this post