How about saving personal.xls with a different name in a shared folder, read only recommended.
Then the team can open the workbook and access all the macros. If opened read only then several can open at same time. You (or any team member) can open without read only to amend the macros or add new ones).
For new macros:
create a macro in your personal.xls, in a separate module then in the Visual Basic Editor use the properties window (F4) to rename the module to something meaningful.
Now export the macro.
Open your Shared Macros workbook.
Alt-F11 to open VBE
Import the file you just created
Save the workbook
Tell the team there is a new macro.
The above approach does not necessitate explaining to the team how to create a personal.xls.
Beware macros that have the same shortcut keys as others your team may have created. Identical names of sub-routines causes fewer issues.
Finally you could develop a macro that opens your shared macros file (read only, with worksheets hidden). Save this in Personal.xls linked to an on-open event. All your macros will always be available just as if they were in personal.xls. Best of both world I reckon. My robust, checked, generic macros are all in one workbook. Those in development or being trialled are in personal.xls (usually).
Thanks,
Gavin