Automate

Winshuttle partner here hello. I just had discussion with customer about organizing Automate Studio Winshuttle usage. 

After our call i send him them a following note. Community: How have you organized? Do you have something add to my remarks? I'm I on the right track at all?

IT-centric

IT is developing scripts based on documentation from the end users

+Good if automation and related templates are complex

+Good if scripts are used every day or weekly by end users and there is little need to do anything else

+Easier to control

-There might be a lot of need for communication

-Development for small improvements (you just accept second best, if you need ask for change)

-Ad hoc needs cannot be addressed so fast

IT Business-driven

Business units that have Winshuttle have their developers

+Good, if automation is needed is simple

+Good if there are a lot of new irregular needs to maintain data

+Often business users get very good at this, then small improvements can be implemented fast for even complex solutions with fast rate

-Licensing cost

-This needs the right culture and without traditional IT ownership culture might be lost if key persons change position

Mixed

-/+It might be that some departments rely on IT, and some are doing things themselves

*Floating developers*

You were thinking if Developer Right could move between departments – at some level, this might work, but more often I see the Winshuttle expert making scripts for other departments. For most of our users Winshuttle development they need is easy, but you get better and maintain your knowledge better if you do it constantly.

------------------------------
Tuomas Silvennoinen
Account Manager
Adsotech Scandinavia Oy
Espoo
------------------------------

Hi Tuomas

You post some interesting perspectives.  You may also want to consider other factors like:  

(1) the value to the business getting the data loaded quickly, often more accurately, all of which can have positive business impacts. 

(2)  Because it is typically easy to create (and maintain) these automations, people in the business can do it.  They typically have a better understanding of the use case, the data involved, and the skillset of the business users who may use them.  As such, they can often serve them better and faster. 

(3) The developer doesn't need a technical skill set (and the costs that go along with it), and can often address business needs more quickly (no waiting in an IT backlog). 

All of this can result in considerable savings and the ability quickly to respond to changing markets/business needs.

There's going to be a session on this in Automate 24 on August 28th.  If you'd like to gain more understanding on this, and see all of the sessions available, please check out this page to register:  Automate 24  

Best Regards, 

Sigrid

------------------------------
Sigrid Kok
Precisely Software Inc.
------------------------------