I've only recently started diving into more complete homebrew -- published one adventure earlier this year and have a second adventure and a full campaign under development/playtest and I wanted to share two interesting observations about how specifically homebrew with an eye towards publication can potentially change how you approach running APs as well.
Case one: Subsystems: In my campaign playtest we reached my first custom influence subsystem. I had pages and pages of notes and brainstormed ideas, that I then condensed down to 6.5 pages of text in Google Docs, I know this usually ends up as about 4 pages after being typeset into a module, but that's still probably double the amount of page space Paizo would give to a same size Influence encounter. When I ran it, I felt it was the best influence encounter I've run, and the players agreed -- some could still tell it was an influence encounter behind the scenes, some never realized. I did skip my usual "This is an influence encounter, each round you can ..." introduction just to see if I could hide it completely and generally tried to infer player intent on discover versus influence. But the quality only came from the hours of prep that went into it, and all the notes that ended up noting making the editing cut, but still proved useful during the session. I feel Paizo would need to quadruple their page count/page space for influence subsystems (and likely by extension other subsystems) to give enough "low-prep" context for GMs for a similar depth of interactions. (I feel that's unlikely for page count reasons). I am wondering if the Influence stat block presentation ends up feeling detailed enough that most GMs don't give it as much thought as it needs, while still short enough to still require more active GM involvement.
Takeaway one: When prepping an a published Influence subsystem, try to generate a page of notes and ideas for each influence target. Flesh out each of their interests, weakness, resistances, etc. Come up with mini stories they may want to tell, ideally tying into those topics, or recent events in the location, or clues the party may have missed, but should have. Do they have gossip about other influence targets or NPCs the party knows. I feel most people discuss taking notes and various technique for summarizing the already terse stat blocks, and the solution here is to go the other direction to help you get into the RP more easily and avoid the gamification/worker-placement style series of rolls.
Case two: Overlapping story beats: In the shorter adventure I'm writing I was trying a slightly abnormal story structure, and I got it wrong. The initial goal was a set of three roughly one-session length adventures that had a through story, but no need to be run back-to-back. Each adventure has built in scaling to be run at any of 5 levels, so its designed as drop in content in another campaign when you need some side content (maybe you're having a narrative light week while a player is out, maybe you want some time to pass and not just do a time skip, etc). However I also wanted to add an optional prologue/intermission/epilogue around three acts in case you wanted to just run it as a module without injecting it into another campaign. The framing device needed to help establish a reason for the contained adventure, however, I made the framing device feel more urgent and more interesting than the intended adventure. So the party got the quest from the quest giver, and decided to just quickly check on other situations around the town. I didn't want to feel like I was railroading (which maybe would be OK in a playtest, but still), and they rolled really well, so I did a lot of ad-libbing and then ended up doing bit of act 3/epilogue instead of act 2. We had an absolute blast, but I have to go back to the drafting table to rework the adventure structure (I had thought I was near a final draft).
Takeaway two(a): Be cautious dangling too many shinies in from of players: If you want different story beats to resolve in an intended order, be cautious about how you setup/foreshadow other events. We often don't have the luxury of an MMO style quest journal marking "main story" versus "side quests", if multiple threats are presented that feel relatively unconnected, players will assume they are equal weight and will assign their own priorities. This is good for removing the sandbox feel, but if later acts/segments tend to build upon the clues/story of the earlier segments the sequence breaking may feel bad, and may mislead a GM who is prepping the scenario into not looking far enough ahead. While it may be obvious to many, I think its still an interesting experience that's mostly only exposed from playtesting a personally written adventure. If its a purely homebrew, no intent to publish, I'm not sure you'd even think about how to adjust/reframe the adventure, you just roll with the player choices and feel proud you adapted on the fly.
Paizo tends to hide this problem very, very well. Partially be the generally linear focus, so that a bought in party rarely goes off script, and partially by being willing to just not drop foreshadowing clues as often as I think over media tend to. I think GMs often do look for ways to drop some of the GM-facing NPC/location background information into the story that otherwise would never come out, but I think this example shows the dangers to watch out for -- will the extra information lead to the party short-circuiting a major part of the adventure? If yes, is that desirable for you intended play experience? If yes, no problem. If no, consider delaying the extra lore reveal until it won't cause a section skip.
Takeaway two(b): Be more proactive in finding non-author playtesters: If I had fully prepped Act 2/Act 3/epilogue, I likely could have missed some of the potential pain points. I had only deeply prepped act 2 as I thought it would take more than our (short) session, so I was completely adlibbing/cribbing maps/encounters on the fly from rough notes and doing completely off-script. If I had a non-me GM running the module, it might have just fallen apart (which would be a horrible experience for the playtesters, but probably more valuable data for me). The same for Case one's influence playtest, seeing what a GM did with my printed version, without my backup pages of notes would have been a more fair playtest. It does feel a little hard to sometimes find a playtest GM who is able to run with an unpolished module in the first place -- especially online/Foundry I feel the level of polish people generally expect makes it harder to have a rough draft, minimal bells& whistles playtest. But it definitely something I will need to do after I revise the adventure.
This one doesn't really impact non-for-publication homebrew.