loading...

re: What are the big differences between working for a "tech company" and being a dev for a "non-tech company" VIEW POST

FULL DISCUSSION
 

I've been a founder of technology startups pretty much my entire life, it's in my blood. However, 2 years ago I accepted a job with an organisation that wanted to go on the journey to become technology led. It's a different beast.

In the non-tech sector:

  • The business isn't counting the cost of feature development and thinks it's paying for everything.

As a software company you are constantly reviewing what makes financial sense to be included. In non-tech our journey has been to identify that "great ideas" from "the people who make all of the money that pays you guys" need equal scrutiny. We all knew we were going on this journey and my colleagues are great, but it's been a nut to crack. Building stuff that matters is what's important to all of us, but old habits die hard. It's really a lot about the whole process of becoming "product" led - more than just the technology.

Software development should be a two way street and the only thing that matters is that we solve the business problem our clients (internal and external) have. The key thing is to understand the business requirement not the feature demands and make sure we are all on the same page.

If anyone is interested I made this video for our investor community (other companies significantly owned by our shareholders) which talks about the issues of going from non-tech project stuff to software company like products.

From that video I think this is one of my key points - just the attitude to failure...

When a non-tech project fails it's a disaster
projects

When a tech company fails it's a learning experience:
products

code of conduct - report abuse